Skip to content

Fix release workflow for branch protection#2

Merged
svperfecta merged 1 commit intomainfrom
fix-release-workflow
Feb 8, 2026
Merged

Fix release workflow for branch protection#2
svperfecta merged 1 commit intomainfrom
fix-release-workflow

Conversation

@svperfecta
Copy link
Contributor

Summary

  • Removes the version bump (npm version patch) and direct commit push to main from the release workflow, which was blocked by org-level branch protection rules.
  • The workflow now reads the current version from package.json instead of bumping it, and only pushes a lightweight git tag.
  • Version bumps are expected to happen in PRs going forward, keeping the release workflow limited to tagging and creating the GitHub release.

Test plan

  • Trigger the Release workflow manually via workflow_dispatch on the main branch with sample release notes.
  • Verify that the workflow reads the version from package.json correctly.
  • Verify that a lightweight tag (e.g., v1.0.1) is created and pushed.
  • Verify that a GitHub release is created with the provided release notes.
  • Confirm no commits are pushed to main by the workflow.

🤖 Generated with Claude Code

Stop bumping version and pushing commits to main (blocked by org-level
branch protection). Instead, read version from package.json and only
push a lightweight tag. Version bumps now happen in PRs.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@svperfecta svperfecta merged commit 6b1f4c1 into main Feb 8, 2026
1 check passed
@svperfecta svperfecta deleted the fix-release-workflow branch February 8, 2026 00:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant