Skip to content

Document cron-first version bumps after docs-eng approval - #3901

Draft
shainaraskas wants to merge 2 commits into
mainfrom
docs/cron-first-version-bumps
Draft

Document cron-first version bumps after docs-eng approval#3901
shainaraskas wants to merge 2 commits into
mainfrom
docs/cron-first-version-bumps

Conversation

@shainaraskas

Copy link
Copy Markdown
Member

Summary

  • Writers self-serve the docs-builder merge after docs-eng approval (this step is not automated).
  • Staging and prod follow cron; the old manual bump/invoke steps remain as backup.
  • Tech leads can no longer approve these PRs.

Note: this branch is 2 commits ahead of main. The extra commit is an applies-to badge fix that was already on the local base; the contribute pages (release-new-version.md, branching-strategy.md) are not on main today (they redirect to assembler environments docs).

Test plan

  • Read docs/contribute/release-new-version.md and confirm merge is manual, cron is staging/prod, backup steps are intact.
  • Confirm no "tech lead" mentions.

Made with Cursor

shainaraskas and others added 2 commits June 19, 2026 10:23
When the highest-version lifecycle in a multi-lifecycle applies_to was
unreleased (e.g. `stack: deprecated, removed 10.0` with current 9.4.2),
the catch-all fallback synthesised "Planned" badge text but left
ShowLifecycleName=true, so the badge rendered the lifecycle name
("Removed") and the forced text ("Planned") side by side.

Honour the documented "use previous lifecycle" rule: when the highest
candidate is future/unreleased, prefer a lower-version applicability
that is current or has no version (so `stack: deprecated, removed 10.0`
now renders as "Stack | Deprecated"). Only fall back to a synthesised
"Removal planned"/"Deprecation planned"/"Planned" label — with
ShowLifecycleName=false — when every applicability is unreleased.

Closes #3537

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Writers merge the docs-builder PR; staging and prod follow cron, with the old manual steps as backup.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

Copy link
Copy Markdown

Label error. Requires exactly 1 of: automation, breaking, bug, changelog:skip, chore, ci, dependencies, documentation, enhancement, feature, fix, redesign. Found:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant