release: prepare 1.0.2 (packaging-only — complete bundle + stable download URL)#248
Merged
Conversation
…nload URL) 1.0.1's install bundle shipped only config.advanced.example.json under a versioned name, and the documented quick start needs config.json.template + a stable pithead.tar.gz URL. Because releases are immutable, 1.0.1's bundle can't be fixed in place — so this ships the corrected bundle as 1.0.2. The published IMAGES are byte-identical to 1.0.1 (re-tagged); nothing in the running stack changes. CHANGELOG [1.0.2] says so and points to 1.0.1 for the feature set. - VERSION + dashboard pyproject -> 1.0.2 - CHANGELOG: thin [1.0.2] packaging entry (the make_bundle/config.json.template fix is #247) Cut with `make release --skip-integration` — the product is unchanged from the matrix- validated 1.0.1. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Cuts 1.0.2, a packaging-only patch, to ship the corrected install bundle. The published images are byte-identical to 1.0.1 — nothing in the running stack changes.
Why a new version
1.0.1's bundle shipped only
config.advanced.example.jsonunder a versioned name, but the (now-merged #247) quick start needsconfig.json.template+ a stablepithead.tar.gzURL. v1.0.1 is immutable, so its bundle can't be patched in place — the only way to ship the corrected bundle (and unbreak the/releases/latest/download/pithead.tar.gzquick-start URL, which 404s today) is a new release.Changes
VERSION+ dashboardpyproject.toml→ 1.0.2CHANGELOG: a thin[1.0.2]entry — states the images are identical to 1.0.1, links to v1.0.1 for the feature set, documents the bundle fix (docs(quickstart): release-bundle install (pull) as the quick start + config.json.template #247) + the install command.Cutting it
make release --skip-integration— the product is unchanged from the matrix-validated 1.0.1, so the live e2e gate would re-test identical bytes. It still runsmake test, builds amd64, smoke-verifies the pushed manifests are amd64, promotes:1.0.2+:latest, and ships the correctedpithead.tar.gzbundle.make testgreen ·changelog_notesextracts the[1.0.2]section cleanly.