Repository navigation
chore(release): prepare 0.1.0 - #22
Merged
Merged
Conversation
Folds the unreleased entries (phases 17-22 and the fixes found during the first real-world run) into the 0.1.0 section, dated, with compare links, so the release workflow publishes complete notes for the tag.
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 the first public release, 0.1.0.
What changed
Unreleasedentries (phases 17–22, plus the fixes from the first real-world run) are folded into## [0.1.0] - 2026-10-20, with compare links at the bottom.scripts/release-notes.mjsextracts this section correctly; the release workflow uses it as the GitHub release notes.package.jsonandsrc/version.tswere already at0.1.0, so nothing to change.Package checks
npm pack --dry-run: 132 files, 107 kB, containing onlydist/,schemas/, README, CHANGELOG and LICENSE. No tests, fixtures or secrets.npx modshift --versionprints0.1.0,analyze --helpworks, andimport('modshift')exposes the API.After merging (manual)
git checkout main && git pull && git tag v0.1.0 && git push origin v0.1.0: the Release workflow re-runs the checks and creates the GitHub release.npm login, thengit checkout v0.1.0 && npm ci && npm publish.npx modshift --version.Generated by Claude Code