release: v0.1.1243 - #3836
Merged
Merged
Conversation
Completes the 0.1.1242 release, which finished only halfway. During the 2026-08-17 GitHub incident the release job published every npm package and created the git tag, then failed creating the GitHub release: HTTP 503: No server is currently available to service your request. (https://api.github.com/repos/veryfront/veryfront/releases) Everything after that step was skipped, including "Trigger server deploy", "Trigger job-runner deploy" and "Trigger sandbox deploy". So npm carries 0.1.1242 while no GitHub release exists and no deploy ever fired. The job cannot be re-run: it creates the tag before the release, so a rerun stops at its own guard -- "Tag v0.1.1242 already exists on source repo. Bump deno.json before releasing." Bumping is the remedy the guard prescribes, and it is safer than hand-assembling a public release with seven binaries and their checksums. Consumers split by install source, so only one is actually blocked: veryfront-agent installs from npm -> unblocked, already on 0.1.1242 veryfront-server installs the compiled -> blocked, needs this release binary from the GitHub release No code changes beyond the version. Contents are 0.1.1242 plus whatever landed on main since, and still include the fixes this chain exists to ship: #3817, #3818 (issue-inbox#548) and #3820/#3821/#3826 (issue-inbox#549).
|
Important Review available on request
Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
📦 Client bundle boundary
A server module in a client graph aborts hydration in the browser. New leaks fail CI; known leaks are tracked in |
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.
Completes the
0.1.1242release, which finished only halfway.What happened
During the 2026-08-17 GitHub incident, the release job published every npm package and created the git tag, then failed creating the GitHub release:
Every step after that was skipped — including Trigger server deploy, Trigger job-runner deploy and Trigger sandbox deploy.
Result: npm carries
0.1.1242, no GitHub release exists, and no deploy ever fired. All seven binaries built and checksummed successfully; only the publish of the release object failed.Why not just re-run the job
The job creates the tag before the release, so a rerun stops at its own guard:
Bumping is the remedy that guard prescribes. It is also safer than hand-assembling a public release with seven binaries and their checksums, which is easy to get subtly wrong in ways nobody notices until a deploy pulls the wrong asset.
Who was actually blocked
Consumers split by install source, so only one:
veryfront-agentveryfront-serverDockerfile:10)Contents
No code changes beyond the version. This is
0.1.1242plus whatever landed on main since, and still carries the fixes this chain exists to ship:gpt-5.4/gpt-5.5)Verification
src/utils/version.test.ts— 1 passed (21 steps). All three version files agree at0.1.1243:deno.json,src/utils/version-constant.ts, and the prebundled hydration runtime.0.1.1243is above the published0.1.1242.Worth fixing separately
The release job is not idempotent: it tags before it publishes the release, so any failure between those two points leaves a version that can never be completed, only superseded. Creating the tag after a successful release — or making the guard tolerate a tag with no matching release — would turn today's outage into a retry instead of a burned version number.