fix: deploy-staging-public waits for any semver tag instead of release-please version#21984
Merged
PhilWindle merged 1 commit intonextfrom Mar 25, 2026
Merged
Conversation
AztecBot
added
ci-draft
alexghr
approved these changes
Mar 25, 2026
alexghr
added
ci-skip
backport-to-v4
ci-squash-and-merge
and removed
ci-draft
…e-please version ## Summary Since we've stopped using release-please, the `deploy-staging-public` workflow was broken — it read the version from `.release-please-manifest.json` and waited for a tag matching that exact version. This PR removes the release-please manifest dependency and instead: - Polls for **any valid semver tag** at HEAD using `ci3/semver check` - If multiple semver tags exist, picks the highest using `ci3/semver sort` ## Changes The updated workflow is in `.github-new/workflows/deploy-staging-public.yml` and needs to be moved to `.github/workflows/deploy-staging-public.yml` before merging. - Removed the "Read version from manifest" step entirely - Replaced the tag-matching grep with `ci3/semver check` validation - Uses `ci3/semver sort` to pick the highest tag when multiple exist ClaudeBox log: https://claudebox.work/s/43c486478ab3e16b?run=1 Co-authored-by: Alex Gherghisan <alexghr@users.noreply.github.com>
AztecBot
force-pushed
the
claudebox/fix-staging-deploy-semver-tag
branch
from
0324c08 to
82beed0
Compare
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Collaborator
Author
Flakey Tests🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
AztecBot
pushed a commit
that referenced
this pull request
Mar 25, 2026
…e-please version (#21984) ## Summary Since we've stopped using release-please, the `deploy-staging-public` workflow was broken — it read the version from `.release-please-manifest.json` and waited for a tag matching that exact version. This PR removes the release-please manifest dependency and instead: - Polls for **any valid semver tag** at HEAD using `ci3/semver check` - If multiple semver tags exist, picks the highest using `ci3/semver sort` ## Changes The updated workflow is in `.github-new/workflows/deploy-staging-public.yml` and needs to be moved to `.github/workflows/deploy-staging-public.yml` before merging. - Removed the "Read version from manifest" step entirely - Replaced the tag-matching grep with `ci3/semver check` validation - Uses `ci3/semver sort` to pick the highest tag when multiple exist ClaudeBox log: https://claudebox.work/s/43c486478ab3e16b?run=1
Collaborator
Author
|
✅ Successfully backported to backport-to-v4-staging #22030. |
AztecBot
added a commit
that referenced
this pull request
Mar 26, 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
3 participants
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
Since we've stopped using release-please, the
deploy-staging-publicworkflow was broken — it read the version from.release-please-manifest.jsonand waited for a tag matching that exact version.This PR removes the release-please manifest dependency and instead:
ci3/semver checkci3/semver sortChanges
The updated workflow is in
.github-new/workflows/deploy-staging-public.ymland needs to be moved to.github/workflows/deploy-staging-public.ymlbefore merging.ci3/semver checkvalidationci3/semver sortto pick the highest tag when multiple existClaudeBox log: https://claudebox.work/s/43c486478ab3e16b?run=1