fix(release): bump version to 0.2.1 and fix workflow for protected branches#290
Merged
Conversation
Signed-off-by: Aseem Shrey <LuD1161@users.noreply.github.com>
The release workflow was failing to bump package.json because main is a protected branch that requires PRs. Changed the version bump step to create a PR with auto-merge enabled instead of pushing directly to main. Signed-off-by: Aseem Shrey <LuD1161@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
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
package.jsonversion from0.2.0to0.2.1mainProblem
The release workflow's "Bump package.json version on main" step was pushing directly to
main, which fails when branch protection requires PRs.Fix
Changed the version bump step to:
chore/bump-version-X.Y.Z)mainTest plan