fix(release): recover assetless v1.8.0 release - #121
Merged
Merged
Conversation
robinvrd
approved these changes
Sep 29, 2026
francoischalifour
marked this pull request as ready for review
September 29, 2026 16:04
francoischalifour
enabled auto-merge (squash)
September 29, 2026 16:05
francoischalifour
pushed a commit
that referenced
this pull request
Oct 1, 2026
🤖 I have created a release *beep* *boop* --- ## [1.9.0](v1.8.0...v1.9.0) (2026-10-01) ### Features * **apps:** package the data app runtime as an npm dependency ([#124](#124)) ([bd807c1](bd807c1)) ### Bug Fixes * **release:** include publication helper in recovery checkout ([#123](#123)) ([2a7b2dc](2a7b2dc)) * **release:** recover assetless v1.8.0 release ([#121](#121)) ([bdf930f](bdf930f)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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
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.
The v1.8.0 release has no assets because its final job tried to install the generated data app with a frozen Bun 1.4 lockfile under Bun 1.1.0. That smoke test failed before asset upload and npm publication.
Keep the complete packaged-app smoke test on the release toolchain. On the minimum supported CLI runtime, test scaffolding, matching the existing compatibility check and documented app build requirements. Allow manual recovery of a published release only when it has no assets and its Git tag matches its pinned commit. This lets the release workflow rebuild, verify, attest, and upload v1.8.0's assets after this change lands.
Verification:
./scripts/verify.shpassed (761 CLI tests, 79 black-box tests, 40 browser tests). The v1.8.0 release currently has zero assets, and its tag points to the pinned release commit.