golem15/summercms
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(33-01): release log for v0.6.1

Browse Source 
- planned contents of framework v0.6.1: the two 33-01 seams and the
  gate script; the six Phase 32 fixes listed as already released in
  v0.5.2
- newest plugin and layer tags with no unreleased commits; versions
  read from git tag in 33-14
- release order and an empty executed-steps table
This commit is contained in:
Jakub Zych
2026-11-04 08:47:58 +01:00
parent 6ea43bb120
commit 21aa4e575f
1 changed files with 67 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

67
.planning/phases/33-seo-output-audit-and-content/33-release-log.md Normal file
View File

@@ -0,0 +1,67 @@
# Phase 33 release log
The phase's release ledger. Plan 33-01 wrote the planned contents; plan 33-14 executes the releases and appends each step to "Executed steps" as it finishes, so a resumed run confirms each `step <n> done` row and skips it: no tag is created twice, no push is forced, a changelog post is published once. Nothing is pushed or tagged before 33-14 (2026-10-28 release cadence: all tags in 33-14).
## Version base (Jakub, 2026-11-04)
The plan text was written against v0.5.1 / v0.5.2. Tags v0.5.2, v0.5.3 and v0.6.0 were released in the meantime, so:
- This phase delivers **SummerCMS v0.6.1**, a patch release: strictly additive (D-106).
- `scripts/check-phase33.sh --additive` compares against the newest tag that does not contain HEAD (computed, currently **v0.6.0**).
- `scripts/check-phase33.sh --marker` diffs from **v0.6.0** (`PHASE33_BASE`).
- Wherever a Phase 33 plan says "v0.5.1" as the base or "v0.5.2" as the target, read v0.6.0 and v0.6.1.
## Planned contents
### Framework v0.6.1 (git.golem15.com/golem15/summercms)
Plan 33-01 seams:
- `feat(signpost): content descriptor fields for dates, parents, authors, media and outline` (561a56c): `pact.ContentDescriptor.Kind` and `Tools` with the `ContentKind*` and `ContentTool*` constants; `pact.ContentRecord.PublishedAt`, `Parents`, `Authors`, `TopHeading`; `pact.ContentLocale.Images`, `Videos`, `Headings`; the value types `ContentRef`, `ContentPerson`, `ContentImage`, `ContentVideo`, `ContentHeading`.
- `feat(cabana): per-request options for plugin field types` (4cd35c9): `pact.FormFieldType.RequestOptions`, merged under the fields.yaml options of each form schema request.
- `test: phase 33 gate script` (6ea43bb, `scripts/check-phase33.sh`).
- Framework commits of later Phase 33 plans, if any, are added here by those plans.
Also on master since v0.6.0, carried by the tag: 22 planning-docs commits of Phase 20 (677e30f..399efed); no code, module or docs change.
Already released, not planned contents (the six Phase 32 fix commits, all in v0.5.2 and every later tag):
- 676ca53 CR-01 check required extension fields on the lifted value (already released in v0.5.2)
- 5471b66 CR-02 gate field type uploads on extension visibility (already released in v0.5.2)
- d660cd0 CR-04 take widget actions dispatched from connectedCallback (already released in v0.5.2)
- 468af06 WR-01 fire record events for hasMany link, unlink and deferred children (already released in v0.5.2)
- 1583651 WR-02 report the request locale's primary tag on record events (already released in v0.5.2; meaning accepted by Jakub on 2026-11-04, see 33-01-SUMMARY)
- 0e187cf WR-07 close the relation and partial routes of hidden owner fields (already released in v0.5.2)
### Plugins and layers
Newest tags when 33-01 ran, and the commits on HEAD since them:
| Repository | Newest tag | Unreleased commits |
|------------|------------|--------------------|
| sm-sitemap-plugin | v0.1.2 | none |
| sm-seo-plugin | v0.1.1 | none (the 22 commits since v0.1.0 are released in v0.1.1) |
| sm-journal-plugin | v0.3.1 | none (the 6 commits since v0.2.5 are released in v0.2.6 to v0.3.1) |
| vue-seo-layer | v0.1.1 | none |
| vue-journal-layer | v0.7.1 | none |
| vue-menu-layer | v0.4.0 | none |
| vue-faq-layer | v0.4.0 | none |
The versions each repository releases in this phase are read from `git tag` in 33-14 (next patch or minor after the newest tag, by what the phase changed there), not fixed here.
## Release order
1. Framework v0.6.1 (tag on master; changelog post on summercms.io/changelog).
2. sm-journal-plugin (requires v0.6.1).
3. sm-sitemap-plugin (requires v0.6.1).
4. sm-seo-plugin (requires v0.6.1 and the sitemap plugin's filter seam).
5. vue-seo-layer.
6. vue-journal-layer, vue-menu-layer, vue-faq-layer.
7. Applications: pointer and pin bumps (sm-demo-app, sm-grzybyfunkcjonalne-app, sm-summercmsio-app, sm-bm-app), each a separate commit after its plugin is pushed; deploys only with Jakub's go-ahead.
Each plugin tag gets a post on summercms.io/changelog/plugins the same day.
## Executed steps
| Step | Repository | Action | Result |
|------|------------|--------|--------|