fix(ci): strip leading v from version input in e2e bundle release workflow#143
Closed
ling-senpeng13 wants to merge 1 commit into
Closed
fix(ci): strip leading v from version input in e2e bundle release workflow#143ling-senpeng13 wants to merge 1 commit into
ling-senpeng13 wants to merge 1 commit into
Conversation
…kflow A manually dispatched run with input v4.0.0-rc1 produced upload target vv4.0.0-rc1 because only the release-event path stripped the v prefix. Normalize the version after both branches instead. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Contributor
Author
|
Closing — not needed. |
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.
Fixes the failure in run 29867346657: the workflow was manually dispatched with
version: v4.0.0-rc1, but theDetermine versionstep only strips thevprefix on the release-event path. The upload step then targeted releasevv4.0.0-rc1, which doesn't exist (release not found).This normalizes the version by stripping a leading
vafter both branches, so dispatch inputs work with or without the prefix.🤖 Generated with Claude Code