publish github-builder-runtime package#1145
Merged
Merged
Conversation
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
publish-github-builder-runtime
branch
from
f69ffc9 to
f9c471e
Compare
tonistiigi
approved these changes
May 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
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.
follow-up docker/github-builder#216 (review)
closes #1144
This change updates the release workflow so each tagged release publishes both
@docker/actions-toolkitand the new@docker/github-builder-runtimepackage: https://www.npmjs.com/package/@docker/github-builder-runtimeThe publish workflow now builds the existing toolkit once, publishes
@docker/actions-toolkit, and then stages a temporary npm package from the same generatedliboutput for@docker/github-builder-runtime. The staged runtime package rewrites only npm metadata, includesnpm-shrinkwrap.json, and publishes with provenance.This implements the runtime-package approach discussed in #1144 (comment). The intent is to keep
@docker/actions-toolkitas the normal library package for Docker action repositories, while givingdocker/github-buildera dedicated npm module whose dependency tree is shrinkwrapped for workflow runtime installs.This addresses the supply-chain concern raised in docker/github-builder#216 (review). Exact npm package versions are immutable, but publishing a shrinkwrap also pins the transitive dependency resolution that consumers get when they install
@docker/github-builder-runtime: https://www.npmjs.com/package/@docker/github-builder-runtime?activeTab=code