fix(release): apply CalVer in manifest mode - #39
Merged
Conversation
The Release Please action ignores release-as in manifest mode. Keep the action for tag creation, but use the pinned Release Please CLI to update the manifest PR with the calculated CalVer override. Co-authored-by: opencode-agent[bot] <219766164+opencode-agent[bot]@users.noreply.github.com>
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
1 participant
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.
Summary
release-asVerification
mise x npm:release-please@17.6.1 -- release-please --versionmise run --dry-run release:prmise x shellcheck@latest -- shellcheck scripts/ci/*.shmise x actionlint@latest -- actionlintgit diff --checkRisk
The workflow uses the action for release creation and the CLI for PR creation because the action currently ignores
release-asin manifest mode. Both are pinned Release Please implementations.Screenshots
Not applicable.