feat(release): publish cf-pushable zip; fix deprecated build hint - #5659
Merged
norman-abramovitz merged 2 commits intoJul 20, 2026
Merged
Conversation
The prerequisite check told operators to run 'make build backend-all', a target renamed to 'make build backend' (see deprecated.mk). Following the message hit the deprecation warning instead of building. Closes cloudfoundry#5657
release-cf.sh looked only for an unqualified dist/bin/jetstream, so it
could not run after 'make build [all]', which cross-compiles to
suffixed names. Teach cf mode to fall back to jetstream-linux-${CF_ARCH}
(amd64 default) so 'make build release cf github' composes in one pass.
The release workflow now builds the cf zip and stages it into
dist/release/ before checksumming, so operators get a cf-pushable
artifact attached to the release instead of only standalone tarballs.
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.
Two related fixes to the release packaging path, both surfaced while cutting v5.0.0-rc.1.
1. Missing-binary hint pointed at a deprecated target (closes #5657)
release-github.shtold the operator to runmake build backend-allwhen binaries were absent. That target was renamed tomake build backend(deprecated.mkmaps the old spelling to aRENAMED:warning). Following the message therefore hit the deprecation notice instead of building. Corrected both occurrences.2. GitHub releases shipped no cf-pushable artifact
The release published six standalone-binary tarballs plus source — none of them
cf push-able. An operator wanting to deploy to Cloud Foundry had to clone and build the zip themselves, despite CF being the primary deployment story.Root cause of why it wasn't already wired in:
release-cf.shlooked only for an unqualifieddist/bin/jetstream, but the release workflow runsmake build all, which cross-compiles to suffixed names (jetstream-linux-amd64, …) and produces no plain binary. Somake build release cf githubfailed at the cf step:Fix: cf mode now falls back to
dist/bin/jetstream-linux-${CF_ARCH}(amd64 default) when the unqualified binary is absent. korifi is unchanged — it still requires its own static build, and its existing static-linkage guard rejects anything else. With the fallback,make build release cf githubcomposes in a single pass.The release workflow now runs
make release cf githuband stages the cf zip intodist/release/before checksumming, so it is checksummed, uploaded, and attached to the GitHub release alongside the platform archives.Verified locally
make release cfagainst a cross-compileddist/now producesstratos-cf-<version>.zip— statically-linked linux/amd64jetstreamat root,Procfile,manifest.yml,config.properties,plugins.yaml,ui/.make release cf github→ stage →create-checksums.sh) lands the cf zip indist/release/and includes it inSHA256SUMS.CF zip is single-arch (amd64). Override with
CF_ARCH=arm64; publishing both arches would be a follow-up.