docs: pre-tag issue gate + TYPO3 14 hidden version surfaces#52
Conversation
- release-process: a Phase-1 step-0 issue gate — never tag over an untriaged known issue from the current work stream; unclear severity is the user's call, a task order incl. 'release' does not delegate it. - ecosystem-detection: composer.json extra.typo3/cms.version is a SEPARATE surface from top-level version (TYPO3 14 deprecation #108345, guarded by VersionConsistencyTest); guides.xml release= attr; Documentation/Changelog.rst; CHANGELOG.md footer compare links. Signed-off-by: Sebastian Mendel <sebastian.mendel@netresearch.de>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
github-actions
Bot
added
documentation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the release documentation by expanding the ecosystem detection reference with specific TYPO3 version surfaces, guides, and changelog requirements, and introducing an "Issue gate" step to the release preparation process to prevent tagging releases with untriaged known issues. The review feedback suggests formatting improvements for consistency, specifically recommending the use of a level 4 header for the "Issue Gate" section and bolding the start of the RST directives list item.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
… item Signed-off-by: Sebastian Mendel <sebastian.mendel@netresearch.de>
|
Two release-discipline learnings from a TYPO3-extension release stream (t3x-nr-llm v0.16.x).
release-process.md— A pre-tag issue gate: before tagging, triage open issues from the current work stream (regression / pre-existing-latent / test-only). Unclear severity — including a self-filed issue whose text says 'production bug' — is the user's decision, not silently shipped; a task order that includes 'release' does not delegate that judgment. Prevents the 'why did you release with known bugs?' failure.ecosystem-detection.md— TYPO3 14 hidden version surfaces:composer.jsonextra.typo3/cms.versionis a separate field from top-level"version"(deprecation #108345, guarded by the extension'sVersionConsistencyTest), plusguides.xmlrelease=attribute,Documentation/Changelog.rst, andCHANGELOG.mdfooter compare-links — all easy-to-miss surfaces.Content-only; no SKILL.md version bump.