Repository navigation
Release 2.0.0 - #49
Merged
Merged
Conversation
2.0.0 is 2.0.0-rc.19 under its final version: no skill, script, or hooks file changes. The release candidates had no exit point, because every sync of Lauren's pstack shipped as another rc. From here each sync is a patch or minor release by what it carries, a major one only when users must act, and each release gets a GitHub release with its CHANGES entry as notes. CONTRIBUTING's Releasing section records the rule.
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.
2.0.0 is 2.0.0-rc.19 under its final version. No skill, script, or hooks file changes, so installed copies only see the version move.
The rc line had no exit point: every sync of Lauren's pstack shipped as another release candidate. This PR ends it and records the rule in CONTRIBUTING's Releasing section:
Each sync's CHANGES entry names the pstack version it moves to, and each release gets a
v<version>tag and a GitHub release with its CHANGES entry as notes.Checks:
bun tools/generate.mjs --checkpasses;bun test tests/550 pass, 46 skip, 0 fail; markdownlint clean on the three edited docs.Note
Low Risk
Release-metadata and documentation only; runtime plugin behavior is unchanged from 2.0.0-rc.19.
Overview
Promotes t3-pstack from
2.0.0-rc.19to stable2.0.0with no changes to skills, scripts, or hooks—only version stamps (VERSION,package.json, marketplace and plugin manifests) and docs.Adds a
## 2.0.0changelog entry stating this is rc.19 under the final number, and extends CONTRIBUTING’s Releasing section with semver rules for future Lauren pstack syncs (patch/minor/major), requiredCHANGES.mdpstack version callouts, andv<version>GitHub releases. README’s pinned-install example now uses#v2.0.0.Reviewed by Cursor Bugbot for commit 950880b. Bugbot is set up for automated code reviews on this repo. Configure here.