Use split publishing workflow#679
Merged
Merged
Conversation
|
bluwy
approved these changes
Jul 1, 2026
mcansh
pushed a commit
to mcansh/remix-fastify
that referenced
this pull request
Jul 7, 2026
…ersion, and publish jobs (#638) This updates the release workflow to mirror the split publishing model from `changesets/action#679`: determine release mode first, then run only the relevant path (`version` or `publish`). The goal is to separate responsibilities in CI and align with the newer Changesets sub-actions. - **Workflow topology** - Replaced the single `release` job with three jobs: - `select-mode` (`changesets/action@v1/select-mode`) - `version` (runs only when mode is `version`) - `publish` (runs only when mode is `publish`) - Routed downstream commenting to depend on `publish` output (`published`) instead of the old combined job. - **Changesets action migration** - Switched from monolithic `changesets/action@v1` invocation to sub-actions: - `changesets/action@v1/version` - `changesets/action@v1/publish` - Updated inputs to sub-action schema: - `script` (replaces `version`/`publish` command inputs) - `commit-message`, `pr-title` (version action) - `create-github-releases` (publish action) - **Behavioral effect** - Release branches now execute an explicit decision phase before taking action. - Version PR creation and package publishing are cleanly isolated, reducing coupling in the workflow logic. ```yaml jobs: select-mode: outputs: mode: ${{ steps.changesets.outputs.mode }} steps: - id: changesets uses: changesets/action@v1/select-mode version: if: needs.select-mode.outputs.mode == 'version' uses: changesets/action@v1/version with: script: pnpm run changeset:version commit-message: "chore: Update version for release" pr-title: "chore: Update version for release" publish: if: needs.select-mode.outputs.mode == 'publish' steps: - id: changesets uses: changesets/action@v1/publish with: script: pnpm run changeset:release create-github-releases: true ```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.