Repository navigation
build(release): upload artifacts_manifest.json to GitHub releases - #4390
Merged
rickeylev merged 1 commit intoNov 1, 2026
Merged
Conversation
Switching the release manifest generator to emit `artifacts_manifest.bzl` (bazel-contrib#4370) dropped the standalone `artifacts_manifest.json` output, and the publish workflow never downloaded `release-manifest` to attach it to the GitHub release. Generate both `artifacts_manifest.bzl` (bundled into the source archive) and `artifacts_manifest.json` via explicit `--bzl-output` and `--json-output` flags, upload `artifacts_manifest.json` in the `release-manifest` workflow artifact, and download and attach it to the GitHub release during publishing. Work towards bazel-contrib#4250
Collaborator
Author
|
AI Disclosure: This PR was created in This is an automatically generated agent comment. |
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.
Switching the release manifest generator to emit
artifacts_manifest.bzl(#4370) dropped the standaloneartifacts_manifest.jsonoutput, and the publish workflow neverdownloaded
release-manifestto attach it to the GitHub release.Generate both
artifacts_manifest.bzl(bundled into the sourcearchive) and
artifacts_manifest.jsonvia explicit--bzl-outputand--json-outputflags, uploadartifacts_manifest.jsonin therelease-manifestworkflow artifact, and download and attach it to theGitHub release during publishing.
Work towards #4250