TL;DR: Publish v0.2.0-alpha.1 to npm incorporating all cleanup and architecture work from this epic.
Context
Part of Epic #35 (v0.2.0 architecture cleanup). This is the final sub-issue — it gates on all 5 preceding sub-issues being merged. The alpha release goes to feature/v0.2.0 branch (not main); main stays at v0.1.4 until Epic 4's final release.
Acceptance Criteria
Scope
In Scope:
- Bump version to
0.2.0-alpha.1 via npm version 0.2.0-alpha.1 --no-git-tag-version (NOT the version:alpha script — that would produce 0.1.5-alpha.0)
- Update CHANGELOG.md
- Build, test, tag, publish
- Create GitHub Release with release notes
- Post-publish verification (fresh install smoke test)
Out of Scope:
- Merge to
main (stays on feature/v0.2.0 until Epic 4)
- External announcements (silent alpha per policy)
Technical Implementation
- Version bump:
npm version 0.2.0-alpha.1 --no-git-tag-version (explicit, not version:alpha)
- Publish:
npm run publish:alpha (runs npm publish --tag alpha; prepublishOnly triggers build)
- Tag:
git tag v0.2.0-alpha.1 after commit
- Release:
gh release create v0.2.0-alpha.1 --prerelease
- Post-publish smoke test:
npm view claude-playwright@alpha version # → 0.2.0-alpha.1
npm view claude-playwright dist-tags # → @latest still 0.1.4
- CHANGELOG entry format: Keep a Changelog style, sections: Changed, Removed, Requires, Notes
- Release notes: Focus on architecture refactor, removed delays, cleaned code. No strategic framing.
Architecture Reference
No architecture decisions from Epic #35 apply directly. Release goes to feature/v0.2.0 branch; @latest npm tag stays on v0.1.4.
Dependencies
TL;DR: Publish v0.2.0-alpha.1 to npm incorporating all cleanup and architecture work from this epic.
Context
Part of Epic #35 (v0.2.0 architecture cleanup). This is the final sub-issue — it gates on all 5 preceding sub-issues being merged. The alpha release goes to
feature/v0.2.0branch (notmain);mainstays at v0.1.4 until Epic 4's final release.Acceptance Criteria
npm view claude-playwright@alpha versionreturns0.2.0-alpha.1v0.2.0-alpha.1(marked as pre-release)npm testpasses before publishnpm publish --dry-run --tag alphasucceeds before actual publishScope
In Scope:
0.2.0-alpha.1vianpm version 0.2.0-alpha.1 --no-git-tag-version(NOT theversion:alphascript — that would produce0.1.5-alpha.0)Out of Scope:
main(stays onfeature/v0.2.0until Epic 4)Technical Implementation
npm version 0.2.0-alpha.1 --no-git-tag-version(explicit, notversion:alpha)npm run publish:alpha(runsnpm publish --tag alpha;prepublishOnlytriggers build)git tag v0.2.0-alpha.1after commitgh release create v0.2.0-alpha.1 --prereleaseArchitecture Reference
No architecture decisions from Epic #35 apply directly. Release goes to
feature/v0.2.0branch;@latestnpm tag stays on v0.1.4.Dependencies