Skip to content

Release v0.2.0#11

Merged
PurpleReverie merged 1 commit into
mainfrom
release/v0.2.0
Jun 1, 2026
Merged

Release v0.2.0#11
PurpleReverie merged 1 commit into
mainfrom
release/v0.2.0

Conversation

@PurpleReverie

Copy link
Copy Markdown
Owner

Summary

Release prep for 0.2.0. Bumps version in package.json, the lockfile, and the CLI's --version output; adds CHANGELOG.md capturing what shipped since 0.1.0.

No functional code changes in this PR — all the behavior shipped in #10.

Why 0.2.0 (not 0.1.1)

A minor bump on the 0.x line because this release:

  • adds a new command (weave clean)
  • adds new flags (--force on lock, --apply/--force on clean)
  • changes observable behavior: lock refuses unpushed commits, post-checkout guards on $3, scan recurses by default, first clones land on the requested branch
  • bumps a dependency to clear a high-severity CVE

That's more than a patch.

Checklist

  • package.json version → 0.2.0
  • package-lock.json synced
  • src/index.ts .version() → 0.2.0
  • CHANGELOG.md written
  • npm run build clean
  • ./tests/init-scenarios.sh 46/46 green
  • Reviewer: when merged, tag and npm publish from a clean tree

Publishing notes (for after merge)

git checkout main && git pull
git tag v0.2.0 && git push origin v0.2.0
npm publish

Bumps version to 0.2.0 across package.json, lockfile, and the CLI's
--version output. Adds CHANGELOG.md summarising the changes since
0.1.0 (recursive scan, weave clean, hardened lock, post-checkout
guard, empty-dir handling, simple-git CVE bump).
@PurpleReverie PurpleReverie merged commit 05759ea into main Jun 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant