chore(main): release 0.2.0#1345
Conversation
89511b6 to
5e58747
Compare
…1349) Adds a shields.io `github/package-json/v` badge to the README badge block that reads the version from the root package.json — release-please bumps that field on every Release-PR merge, so the badge tracks the release line (0.1.0 today, 0.1.1 when #1345 merges) with zero README edits and no hardcoded number in the markdown. Chose package-json/v over v/release so it renders correctly right now, independent of when the v0.1.0 GitHub Release is published. Keeps the low-churn `Status: alpha` badge as-is (maturity axis, not version) and drops the now-stale "First public release is in progress" prose so it can't re-drift. Closes #1346 Signed-off-by: Piotr Swierzy <piotr.swierzy@blockydevs.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ea4b346 to
edfd179
Compare
piotrswierzy
left a comment
There was a problem hiding this comment.
/pr-review — chore(main): release 0.2.0 (release-please)
Auto-generated release PR (CHANGELOG + version bumps, 3 files, +27/-2). Reviewed as a release artifact, not hand-written code.
- Semver is correct — the window
v0.1.0…v0.2.0contains user-facing features (viewer read-access #1363, one-command demo #1365, several inFakt/invoicing features), so a minor bump (0.1.0 → 0.2.0) is the right call, not a patch. - Changelog fidelity — the Features/Bug-Fixes entries map to real merged commits on
main; base is6102b244(includes the #1391 WooCommerce variant-picker merge), so the release line is current. - Mechanism — standard release-please output; the version field it bumps is the same single source the README badge (#1346) and
GET /v1/healthread, so no manual version edits are needed elsewhere.
mergeable_state: blocked is branch protection (needs this approval + green checks), not a content problem.
✅ Approve — merge to cut 0.2.0 whenever you're ready to tag. This is the release gate; nothing to change in the PR itself.
7e91410 to
20bcf14
Compare
piotrswierzy
left a comment
There was a problem hiding this comment.
/pr-review — chore(main): release 0.2.0 (re-affirm)
Re-checked after the head moved — the changelog now also folds in #1397 (WooCommerce demo boot), #1393 (PS healthcheck), #1389 (invoice timestamptz), and #1391 (WooCommerce variant picker), all merged to main. Entries map to real commits, base tracks the current main tip, and the bump stays 0.2.0 (minor is correct — user-facing features in the window). Standard release-please artifact; the version field it bumps is the same single source /v1/health + the README badge read.
✅ Approve — merge to cut/tag 0.2.0 when ready. mergeable_state: blocked is branch protection (this approval + checks), not content.
b6a635d to
b845871
Compare
4768d32 to
7285771
Compare
7285771 to
6522ffa
Compare
🤖 I have created a release beep boop
0.2.0 (2026-07-14)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.