Repository navigation
v0.8.0
Breaking changes
- Updates the action wrappers for the MonoChange 0.8 CLI command API.
- Removes default usage of project-specific
monochange runworkflow aliases in favor of stablemonochange step ...commands. - Changeset policy now runs
monochange step affected-packagesinstead of the oldmc step:affected-packagescommand shape.
Upgrade guide: changeset-policy from v0.7 to v0.8
The changeset-policy action inputs are intentionally unchanged, so most workflows only need to bump the action ref:
- uses: monochange/actions/changeset-policy@v0.7
+ uses: monochange/actions/changeset-policy@v0.8or pin the exact release:
- name: run changeset policy
uses: monochange/actions/changeset-policy@v0.8.0
with:
changed-paths: ${{ steps.changed.outputs.all_changed_files }}
labels: ${{ join(github.event.pull_request.labels.*.name, ',') }}
github-token: ${{ secrets.GITHUB_TOKEN }}If your workflow provides MonoChange itself, make sure the command on PATH is now monochange from MonoChange 0.8.x:
- setup-monochange: false # required `mc` on PATH in v0.7
+ setup-monochange: false # requires `monochange` on PATH in v0.8If you pass a custom command, update it from mc to monochange:
- setup-monochange: mc
+ setup-monochange: monochangeFor projects using a development shell, point the action at the shell command that exposes MonoChange 0.8:
- name: run changeset policy
uses: monochange/actions/changeset-policy@v0.8.0
with:
setup-monochange: devenv shell monochange
changed-paths: ${{ steps.changed.outputs.all_changed_files }}
labels: ${{ join(github.event.pull_request.labels.*.name, ',') }}No input rename is required for changed-paths, labels, skip-labels, comment-on-failure, dry-run, or debug.
Added
- Adds dedicated action variants for
check,release-preview,release-record,open-release-request,tag-release,publish-readiness, andpublish-packages. - Adds top-level path actions for the new variants while keeping root action dispatch via the
nameinput.
Validation
pnpm allpassed before tagging.