Repository navigation
chore(release): prepare v0.0.1 - #5
Merged
Merged
Conversation
Version 0.0.1 in package.json and the lockfile, the CHANGELOG's Unreleased section released as 0.0.1, and every install spec at #v0.0.1. The docs test strips any #v<x.y.z> install spec instead of #v0.0.0 alone, and the host test reads the status version from package.json instead of the literal 0.0.0.
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.
Prepares v0.0.1 as opencode-gws #35 did: version 0.0.1 in package.json and the lockfile,
node scripts/changelog.mjs release(Unreleased → [0.0.1] - 2026-11-12, the issue #1 fixes merged in #3), and every install spec at #v0.0.1. Beyond the gws model, two test lines that pinned 0.0.0: the docs test now strips any #v<x.y.z> install spec, and the host test reads the status version from package.json.