release: v0.11.0 - #128
Merged
Merged
release: v0.11.0#128
Conversation
Minor, not patch: `upload-failure-reports` is a new input on build-jupyter-cache, so this is more than bug fixes even though the headline changes are two alerting fixes. Also merges the two separate `### Fixed` blocks the Unreleased section had accumulated — the #123 work was written above the #122 entries rather than into them — and orders the merged block oldest-first, so the #123 entry reads after the #122 entries it refers back to. Contents: the container-mode alerting fix (#83, #122), the abort-before-builds fix (#123, #127), the harness relevance gate (#116), and container smoke tests that can actually fail (#108). CONTRIBUTING step 5 (drop @v0 workarounds this release makes obsolete): none outstanding — the `@v0` mentions in test-actions.yml are comments describing the structural limitation, not workarounds. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Prepares the repository for the v0.11.0 release by updating CHANGELOG.md only (no action/runtime code changes), promoting the prior Unreleased entries into a dated release section and normalizing section ordering.
Changes:
- Moves the Unreleased changelog entries into a new
0.11.0release section. - Reorders and consolidates entries under Added / Changed / Fixed to match prior sections and Keep a Changelog structure.
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.0. CHANGELOG-only — no action code changes.
Why minor rather than patch
The headline changes are two bug fixes, but
upload-failure-reportsis a new input onbuild-jupyter-cache(verified absent atv0.10.0, present onmain), so this is more than a patch under the 0.x convention in CONTRIBUTING.What's in it
Eight commits since
v0.10.0, in four themes:== 'false'against an output that was''paths:filters, making the harness safe to require onmaincontainer:jobsWhy this release matters more than the version bump suggests
build-jupyter-cachecallssetup-environmentandbuild-lecturesat the pinned@v0ref, andv0still points atv0.10.0— so neither alerting fix reaches any consumer untilv0moves in the release steps below. The canary (test-actions-lecture-intro) runs against@v0, and the issue-filing path is the half the in-repo harness structurally cannot cover, so movingv0is also what finally puts that path under observation.Note separately that
lecture-dppins exact tags at@v0.8.0, so it will still not have either fix after this release — bumping it is a follow-up, tracked in PLAN.Changelog housekeeping
The Unreleased section had accumulated two separate
### Fixedblocks (the #123 work was written above the #122 entries rather than merged into them). They are merged into one, ordered oldest-first so the #123 entry reads after the #122 entries it refers back to. Sections are now Added / Changed / Fixed, matching Keep a Changelog and the earlier released sections. A guard in the script that made the edit asserted no entry was dropped or duplicated in the reorder.Release steps after merge (CONTRIBUTING §"Creating a Release")
Tag
v0.11.0, force-move the floatingv0to it, publish the GitHub Release. Step 5 — drop@v0workarounds this release makes obsolete — is a no-op: the@v0mentions intest-actions.ymlare comments describing the structural limitation, not workarounds, and CONTRIBUTING records "Currently outstanding: none".🤖 Generated with Claude Code