release: v0.11.1 - #132
Merged
Merged
release: v0.11.1#132
Conversation
Patch: one bug fix, no behaviour added. The judgement call worth recording — v0.11.0 was a minor because it added an input, and this adds an output (`deployment-url`), which is strictly the same category of additive surface growth. Called a patch anyway on two grounds: the changelog files the change under Fixed because the new output is incidental to the fix rather than a new capability (it preserves information the fix would otherwise have discarded), and `deploy-url`'s previous value was non-deterministic — alias or hash depending on the wrangler release — so no consumer could safely have depended on it. Contents: preview-cloudflare links the stable pr-N alias rather than the per-deployment hash (#14, #131). CONTRIBUTING step 5: no @v0 workarounds outstanding — the @v0 mentions in test-actions.yml are comments describing the structural limitation. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Cuts the v0.11.1 release by updating the changelog to document a preview-cloudflare fix (PR comments now prefer the stable pr-{number} Pages alias URL and clarifies the related nondeterministic URL-parsing behavior).
Changes:
- Add a new 0.11.1 release section dated 2026-08-07.
- Document the
preview-cloudflarePR-comment URL fix and the relateddeploy-urlnondeterminism/deployment-urlpreservation.
mmcky
added a commit
that referenced
this pull request
Aug 11, 2026
Five stale facts, all overtaken by v0.11.1 (#131/#132): - latest release read v0.11.0 - backlog item 5 (#14, the Cloudflare alias URL) was still listed as open although #131 shipped it; its disposition row still said "Still valid" - the dependency policy still pinned the baseline to anaconda=2025.12, four months after #95 migrated both images to 2026.06 - the rollout section still showed lecture-dp and lecture-python.myst on @v0.8.0, contradicting the "every consumer now tracks @v0" line above it The disposition table covered 8 issues while 21 are open, so it was no longer usable as a status view. Adds a second table for everything opened after the July review, including #135. Item 3's "=2025.12" is left as-is: it narrates the misconception that produced #86/#87, not the current baseline. Co-Authored-By: Claude Opus 5 (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
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 v0.11.1. CHANGELOG-only.
What's in it
One fix:
preview-cloudflarelinks the stablepr-{number}branch alias in PR comments rather than the per-deployment hash URL (#14, #131). Also fixes a latent bug found alongside it — the oldgrep … | head -1returned whicheverpages.devURL wrangler printed first, which meantdeploy-urlwas the alias on one wrangler release and the hash on another, with nothing pinning which.Why this one needs its own release
Unlike the alerting fixes in v0.11.0, this does not reach anyone through the
@v0chain.build-jupyter-cachepulls its siblings in at@v0, so moving that tag delivered those fixes; the preview actions are called directly by consumers, so the fix is unreachable until a release exists to point at.Patch, not minor — the judgement call
v0.11.0 was a minor because it added an input, and this adds an output (
deployment-url), which is strictly the same category of additive surface growth. Called a patch on two grounds, recorded here so the inconsistency is deliberate rather than accidental:deployment-urlexists only to preserve information the fix would otherwise have discarded — the hash URL used to land indeploy-urlsome of the time — rather than to add a capability.deploy-url's previous value was non-deterministic, varying with the wrangler release the runner happened to install. No consumer could safely have depended on it, so redefining it to always be the alias is a fix rather than a contract change.Happy to re-cut as v0.12.0 if you read it the other way.
Release steps after merge
Tag
v0.11.1, force-movev0, publish the GitHub Release. Step 5 is a no-op again — CONTRIBUTING records "Currently outstanding: none", and the@v0mentions intest-actions.ymlare comments about the structural limitation, not workarounds.Consumer note
The only consumer of
preview-cloudflaretoday is via the preview rollout;lecture-python.mystusespreview-netlifyand is still on exact@v0.8.0, so it is unaffected either way. It remains the last exact-pinned consumer — worth moving to@v0for consistency, but not urgent, since this fix does not touch its action.🤖 Generated with Claude Code