Repository navigation
Cuts the 0.11.0 release prep - #192
Merged
Merged
Conversation
Bumps `@version` to 0.11.0 and promotes the one changelog fragment, `changelog.d/sui-25h.md`, into a new `## [0.11.0]` section of CHANGELOG.md, its bullet carried over byte for byte under `### Changed`, and deletes the fragment. The heading keeps the file's own form, the bracketed version and the local date with no separator. A minor because a documented live behaviour changes: the Livebook inspector's datamodel pane follows the scrubber. No public function, option or runtime dependency changes; the trace wire format is untouched. Both install pins, README.md and docs/ops-embedding.md, move to the exact-minor `~> 0.11.0`. Refs: sui-mmrk
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.
Summary
The release prep for statifier_ui 0.11.0, under
.claude/wurk/release.md.mix.exs:@versionmoves from 0.10.2 to 0.11.0.CHANGELOG.md: a new## [0.11.0] 2026-10-11section (the file's own heading form, the local date) with a short lead paragraph and the promoted fragment's bullet carried over byte for byte under### Changed.changelog.d/sui-25h.md: the one fragment on main, promoted and deleted;changelog.d/README.mdstays.README.mdanddocs/ops-embedding.md: both install pins move to the exact-minor~> 0.11.0.These are exactly the files the extension's table lists; nothing else is touched.
Why a minor
The one fragment is a
### Changedentry: the Livebook inspector's datamodel pane (StatifierUI.Kino.inspect/3) follows its scrubber, a documented live behaviour that changes (the pane following the scrubber was ruled by the operator, 2026-10-10). The onlylib/change sincev0.10.2is inlib/statifier_ui/kino.ex: the moduledoc's scrubber paragraph and the pane render passing the inspector's options toStatifierUI.Inspector.datamodel/2, which already took them atv0.10.2. No public function, option or runtime dependency changes (the only requirement line that moved sincev0.10.2is the dev-onlyex_quality), and the trace wire format is untouched.Closed sets: neither the fragment nor the
lib/diff sincev0.10.2adds a member to a vocabulary a host pattern-matches (no new trace type, option value, reason or return shape).Left as is
The
CHANGELOG.mdpreamble linkschangelog.d/README.mdat thev0.10.1tag. That file is unchanged betweenv0.10.1and main, so the link resolves to the current text; it is left alone here rather than pointed at a tag that does not exist until after this merges.Gate
Full
mix qualitygreen on the staged tree of this commit (every stage passed; the three skipped stages are the repo's known ones: Diataxis opt-in, Gettext and Sobelow not installed), run while holding the repo's gate lock and a machine slot continuously through the commit. The committed tree is byte-identical to the tree the gate ran on, so the commit was made directly after that run without a second one.After the merge
The conductor merges, pulls main, tags
v0.11.0at the merge commit and pushes the tag; the release workflow (.github/workflows/release.yml) publishes on the tag push. This PR tags nothing and publishes nothing.