Version Packages - #8
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
subtext-verify@0.3.0
Minor Changes
9f81179: Reframe Subtext Verify as a companion plugin to Subtext and remove skill-name
collisions and duplicated guidance. Verify stays a plugin (manifests, marketplace
install, SessionStart proof-trigger hook), but now explicitly requires Subtext
installed first and no longer re-ships anything Subtext already owns.
subtext-shared→subtext-verify-shared(slimmed to verify-only deltas; general conventionsdefer to Subtext's
subtext-shared), andsubtext-using-subtext→subtext-verify-using(the SessionStart hook now injects this).subtext-sightmapschema fork (it duplicated Subtext's canonicalsightmap-authoring);subtext-recipe-sightmap-setupandsubtext-onboardnow reference
sightmap-authoring.subtext-setup-pluginskill; its tunnel-serverconnectivity and PyYAML-dependency notes are folded into
subtext-tunnel.subtext-tunnelstdioserver and relies on base Subtext for the shared
subtextHTTP server.subtext-live.Every skill name is now unique across a combined Subtext + Verify install, so the
two compose without collisions.
Note
Low Risk
Release-metadata only (version bumps, changelog, changeset cleanup); no runtime code changes in this diff.
Overview
Automated Changesets release for
subtext-verify@0.3.0. The diff bumps the version from0.2.0to0.3.0inpackage.json, Claude/Codex/Cursor plugin manifests, andgemini-extension.json, and adds the 0.3.0 section toCHANGELOG.md.The changelog documents the minor release already landed on main: Verify is framed as a companion to base Subtext (requires Subtext first), with renamed skills (
subtext-verify-shared,subtext-verify-using), removal of duplicated sightmap/setup skills in favor of Subtext’ssightmap-authoring, tunnel-only MCP in Verify (sharedsubtextHTTP server comes from base Subtext), and consolidated tunnel/setup guidance insubtext-tunnel.The pending changeset file
.changeset/verify-skills-only.mdis removed after versioning, which is normal for this release workflow.Reviewed by Cursor Bugbot for commit 956e5da. Bugbot is set up for automated code reviews on this repo. Configure here.