This repository was archived by the owner on Aug 24, 2026. It is now read-only.
Repository navigation
Document the release procedure - #51
Merged
Merged
Conversation
Releasing 1.1.0 surfaced two things that were not written down anywhere: which branch users actually install from, and that the bundle version lives in two files a contract test keeps in sync. docs/releasing.md records the per-PR changelog duty, how to choose the version by installed-copy impact, and the tag-and-publish steps. It also notes the rough edge that BUNDLE_VERSION moves only at release, so an install from main mid-cycle records the previous version. README gains the tag-pinned install form. Both `#v1.1.0` and the `/tree/v1.1.0` URL were verified against this repo with `skills add --list`, which resolved `@ v1.1.0` and found the skill without installing. npm test passes (184 tests, 182 pass, 2 skipped).
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Releasing 1.1.0 surfaced two facts that were written down nowhere: which branch
users actually install from, and that the bundle version lives in two files kept
in sync by a contract test. This records them.
docs/releasing.mdcovers the per-PR changelog duty, how to choose the versionby installed-copy impact, and the tag-and-publish steps. It also records the
rough edge that
BUNDLE_VERSIONmoves only at release, so an install frommainmid-cycle writes the previous version into
.fusion-install.json.README gains the tag-pinned install form, so users are not forced to track
main.Verification
npm test- 184 tests, 182 pass, 2 skipped, 0 failskills add --list, whichresolved
@ v1.1.0and found the skill without installing anything:mihneaptu/opencode-fusion#v1.1.0https://github.com/mihneaptu/opencode-fusion/tree/v1.1.0Deliberately not included
The install command also appears in
site/index.html(twice),site/docs.html,and
site/llms.txt. Those are unchanged: the default install should stay theuntagged one, and adding a pin note to every surface is a separate decision.
Docs-only change, so no changelog entry.