Repository navigation
Conversation
dmikusa
force-pushed
the
add-multi-implementation
branch
from
October 28, 2026 03:19
26bef38 to
7375d02
Compare
Add a multi-implementation set for repositories that package a combined buildpack plus one buildpack per component. Repositories provide a multi-implementation.json at the root describing the combined buildpack, the components, image names, and the libpak-tools command. The create-draft-release, push-buildpackage and update-dependencies workflows derive their matrices and artifact names from that file. The update-dependencies workflow also gains the warning check that jvm-vendors previously carried as a local customization, and package.sh is now generic so jvm-vendors and build-tools can share it.
dmikusa
force-pushed
the
add-multi-implementation
branch
from
October 28, 2026 03:21
7375d02 to
e93fae3
Compare
dmikusa
marked this pull request as draft
October 28, 2026 03:58
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.
Summary
Adds a new
multi-implementationworkflow set for repositories that package a combined buildpack plus one buildpack per component, such asjvm-vendorsandbuild-tools.Repositories provide a
multi-implementation.jsonat the repository root:{ "combined": "build-tools", "integration": false, "libpak-tools": { "command": "build-build-tools", "artifact-flag": "tools", "include-all-flag": "include-all-tools" }, "buildpacks": [ { "name": "build-tools", "image": "build-tools" }, { "name": "leiningen", "image": "leiningen-dev" } ] }The set includes:
create-draft-release.yml— derives the release-note matrix from the config, uses the full release notes action for the combined buildpack andjam summarizefor components, and optionally runs integration tests (configintegrationflag)push-buildpackage.yml— derives the push matrix and image names from the configupdate-dependencies-from-metadata.yml— the shared template plus thehas-warningscheck thatjvm-vendorspreviously carried locallyscripts/package.sh— generic packaging driven by the config andlibpak-toolsIt also updates
bootstrap.sh,sanity.shand the README for the new set.Follow-up PRs will switch
jvm-vendorsandbuild-toolsto this set.Note
This PR was written by opencode and reviewed by a human.