Repository navigation
SK-3261 Bump flowvault version to 1.3.0 - #455
Merged
Merged
Conversation
The public release workflow can no longer push its version-bump commit to main: the org ruleset prod-branch-protection requires a pull request and the release PAT is not on its bypass list. With the pom already at 1.3.0, the workflow's commit step finds nothing staged and skips the push. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep Findings: Issues with Error level severity are found (Error is Highest severity in Semgrep), Please resolve the issues before merging. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #455 +/- ##
==========================================
Coverage 91.29% 91.29%
- Complexity 0 571 +571
==========================================
Files 174 174
Lines 7401 7401
Branches 1024 1024
==========================================
Hits 6757 6757
Misses 422 422
Partials 222 222
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
skyflow-bharti
approved these changes
Oct 29, 2026
Promptless documentation updates
|
aadarsh-st
approved these changes
Oct 29, 2026
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.
Why
flowvault/v1.3.0(run 40876207285) failed at Commit changes. The push of the[AUTOMATED] Public Release - 1.3.0commit tomainwas rejected withGH013: Changes must be made through a pull request.prod-branch-protection(added 2026-10-09, updated 2026-10-28), now requires a PR for every change to the default branch. The release service-account PAT can bypass the repo rulesets, but it is not on this ruleset's bypass list. Every public release before this ruleset existed (most recently 1.2.0 on 2026-09-10) pushed straight tomain.Goal
flowvault/pom.xmlto1.3.0onmainthrough a PR. When the release runs again, the bump step leaves the pom unchanged, Commit changes finds nothing staged and exits 0 without pushing (shared-build-and-deploy.yml, "nothing to commit" guard), and the build and deploy proceed.Testing
scripts/bump_version.sh 1.3.0 "" flowvaultlocally against this pom. The output is byte-identical to the input, so nothing is staged when the workflow runs.flowvault/v1.3.0release targetingmain, with the tag on this PR's merge commit. Don't merge other PRs that touchflowvault/pom.xmlbefore the release runs.🤖 Generated with Claude Code