You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Publish-PSModule action currently handles both creating a GitHub Release and publishing to the PowerShell Gallery as part of a single workflow step or tightly coupled process. This makes it harder to debug failures, retry individual publishing steps, or add new registries in the future.
Request
The GitHub Release creation and the PowerShell Gallery publishing should be separated into distinct, independent steps in the workflow.
Acceptance criteria
GitHub Release creation is a separate step from PSGallery publishing
Each step can succeed or fail independently
Failures in one step do not block the other (unless explicitly configured)
The workflow summary clearly shows the status of each step
Technical decisions
To be determined during implementation planning.
Implementation plan
Identify the current coupling between GitHub Release creation and PSGallery publishing in Publish-PSModule
Separate into two distinct jobs or steps
Ensure each step reports its own status independently
Update the workflow to handle partial failures (e.g., PSGallery publish fails but GitHub Release succeeds)
Context
The Publish-PSModule action currently handles both creating a GitHub Release and publishing to the PowerShell Gallery as part of a single workflow step or tightly coupled process. This makes it harder to debug failures, retry individual publishing steps, or add new registries in the future.
Request
The GitHub Release creation and the PowerShell Gallery publishing should be separated into distinct, independent steps in the workflow.
Acceptance criteria
Technical decisions
To be determined during implementation planning.
Implementation plan