Repository navigation
release: 0.2.0 - #42
Merged
Merged
Conversation
Minor bump, because §11.1 landed and the export seam changed behaviour. The one version line every port ships at (ADR-4), so all twenty-three tags move together and the four manifests that state a version say 0.2.0. Since 0.1.7: - `inst.capability(name)`, §11.1's declared-capability read, which is new public API rather than a fix. - `exports` splits its spec at the LAST slash, so a scoped name like `@voxgig/thing/api` resolves the export rather than the scope. That is a behaviour change for any ref holding more than one slash. - `probe` carries a second scalar key, and `dep` holds a resource in the five ports where it did not. No breaking change: every existing call, ref shape and corpus entry behaves as it did. Releases the versions already on main - `tag.yml` with port `all`, which `publish.yml` then picks up for the two npm ports. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVMgjjwQfTJ2rXz637Wpk8
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Version bump only —
VERSIONplus the four manifests that state one andtheir lock files. No behaviour change in this diff;
make versionspasses, and
npm cistill resolves in both npm ports.Minor, not patch, because two things since 0.1.7 are more than fixes:
inst.capability(name)— §11.1's declared-capability read. Newpublic API, in every port.
exportssplits its spec at the LAST slash, so a scoped name like@voxgig/thing/apiresolves the export rather than the scope. That is abehaviour change for any ref holding more than one slash, and the corpus
now pins it.
Also in that window:
probecarries a second scalar key,depholds aresource in the five ports where it did not, the export how-to, and the
Vale half of the prose gate.
No breaking change — every existing call, ref shape and corpus entry
behaves as it did. ADR-4 keeps one version line for the whole repository,
so all twenty-three ports move together.
VERSION@voxgig/plugin@voxgig/plugin-jspython/pyproject.tomlrust/Cargo.tomlOnce this merges,
tag.ymlruns viaworkflow_dispatchwith portall,which writes the twenty-three tags;
publish.ymlpicks up the two npmones from their tags.
🤖 Generated with Claude Code
https://claude.ai/code/session_01CVMgjjwQfTJ2rXz637Wpk8
Generated by Claude Code