fix: Move BigQuery insertion after release step #6477
Merged
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.
Problem
The BigQuery insertion step was giving nothing in the version tag because it attempted to access
steps.create_release.outputs.version_tag
before the release step had run, resulting in missing version data in our bundle size tracking.Solution
Reordered the GitHub Actions workflow steps to ensure the BigQuery insertion happens after the release step, when the version tag is available.
Changes
create_release
stepTest plan
Changelog