fix(ci): resolve invalid context access for new_version in release workflow #532
+9
−9
Conversation
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
…rkflow Updates the release.yml workflow to correctly define and access the new_version output using step outputs for version passing instead of environment variables, resolving the "Context access might be invalid" warning.
|
For the love of god someone PLEASE merge this, it has been a problem for years |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
This PR resolves the "Context access might be invalid: new_version" error in the release workflow.
Changes
new_versionvariable between steps using$GITHUB_OUTPUT.steps.bump_version.outputs.new_versioninstead of potentially undefined environment variables.Context
The workflow was previously flagging a potential invalid context access. This change ensures the version number is reliably passed to the branch creation and PR generation steps.
Note
While this is not a direct fix for #222, a similar issue occurred in this repository. This adjustment to the workflow could serve as an example of how the symptoms could potentially be resolved.