larvit/plainpages
3
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Release the gate change as 0.3.0, and start a changelog #105

Merged
lilleman merged 1 commits from contract-0-3-0 into main 2026-09-03 18:01:32 +02:00
Conversation 0 Commits 1 Files Changed 8
+69 -11
lilleman commented 2026-09-03 17:59:02 +02:00
Owner
Copy Link
Copy Source

The 0.3.0 contract generation was never tagged — released versions run 0.1.0, 0.2.0, 0.2.1 — so
releasing the session gate as 0.4.0 would spend a minor on a state no adopter ever received. This
puts HOST_API_VERSION back to 0.3.0 and rewrites the nine author-facing apiVersion samples with
it, so 0.3.0 is the release that carries the gate change.

It also repairs the release path as a side effect: with the constant at 0.4.0 and the last tag at
v0.2.1, a Renovate auto-release computes v0.2.2 and release.yml's contract check refuses it, so
nothing could publish. Tagging v0.3.0 from this puts the two back in step.

CHANGELOG.md starts here, covering everything since v0.2.1 — the session gate and the
exactly-one-gate rule, the filter-bar multiselect control, the emailless-identity session fix,
and Node 24.20.0 — with the two steps a plugin author has to take.

The 0.3.0 contract generation was never tagged — released versions run 0.1.0, 0.2.0, 0.2.1 — so releasing the session gate as 0.4.0 would spend a minor on a state no adopter ever received. This puts `HOST_API_VERSION` back to 0.3.0 and rewrites the nine author-facing `apiVersion` samples with it, so 0.3.0 is the release that carries the gate change. It also repairs the release path as a side effect: with the constant at 0.4.0 and the last tag at v0.2.1, a Renovate auto-release computes v0.2.2 and `release.yml`'s contract check refuses it, so nothing could publish. Tagging v0.3.0 from this puts the two back in step. `CHANGELOG.md` starts here, covering everything since v0.2.1 — the `session` gate and the exactly-one-gate rule, the `filter-bar` `multiselect` control, the emailless-identity session fix, and Node 24.20.0 — with the two steps a plugin author has to take.
lilleman added 1 commit 2026-09-03 17:59:02 +02:00
Release the gate change as 0.3.0, and start a changelog
CI / full-gate (push) Successful in 2m50s
Details
Mirror / github-mirror (push) Successful in 4s
Details
Release / retag-image (push) Successful in 22s
Details
Release / publish-overview (push) Successful in 3s
Details
54956fe627
lilleman merged commit 54956fe627 into main 2026-09-03 18:01:32 +02:00
lilleman deleted branch contract-0-3-0 2026-09-03 18:01:32 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claes.eismar.se lilleman (Lilleman auf Larv) martin.siden renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: larvit/plainpages#105
Delete Branch "contract-0-3-0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?