Skip to content

chore(release): prepare 0.1.0 - #22

Merged
NeyorDEV merged 2 commits into
mainfrom
chore/release-0.1.0
Oct 20, 2026
Merged

NeyorDEV merged 2 commits into
mainfrom
chore/release-0.1.0

Conversation

@NeyorDEV

Copy link
Copy Markdown
Owner

Prepares the first public release, 0.1.0.

What changed

  • CHANGELOG: the Unreleased entries (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.mjs extracts this section correctly; the release workflow uses it as the GitHub release notes.
  • Version: package.json and src/version.ts were already at 0.1.0, so nothing to change.
  • PROGRESS.md:

Package checks

  • npm pack --dry-run: 132 files, 107 kB, containing only dist/, schemas/, README, CHANGELOG and LICENSE. No tests, fixtures or secrets.
  • The tarball installed in an empty folder works: npx modshift --version prints 0.1.0, analyze --help works, and import('modshift') exposes the API.

After merging (manual)

  1. 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.
  2. npm login, then git checkout v0.1.0 && npm ci && npm publish.
  3. Check with npx modshift --version.

Generated by Claude Code

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.
@NeyorDEV
NeyorDEV merged commit c242c09 into main Oct 20, 2026
2 checks 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