Skip to content

docs: retire v2-docs-stable; RTD uses master + release tags - #775

Merged
jepegit merged 2 commits into
masterfrom
768-retire-v2-docs-stable
Jul 28, 2026
Merged

docs: retire v2-docs-stable; RTD uses master + release tags#775
jepegit merged 2 commits into
masterfrom
768-retire-v2-docs-stable

Conversation

@jepegit

@jepegit jepegit commented Jul 28, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add .issueflows/04-designs-and-guides/docs-on-master.md: docs on master; v2-docs-stable retired; RTD latestmaster, stable←release tags.
  • Update marimo / branching / release-procedure / this-project / dev_docs.md so nothing tells agents to use v2-docs-stable.
  • HISTORY Unreleased note.

Tag for RTD: v2.1.0 already exists on master (no new tag needed). Point RTD stable at that tag (or “latest non-prerelease tag”) in the RTD admin UI.

Test plan

  • Skim docs-on-master.md + dev_docs.md for clear instructions
  • RTD admin: confirm latest=master, stable=v2.1.0 (or auto from tags); rebuild stable if needed
  • Optional: delete remote v2-docs-stable after RTD no longer references it

Refs #768

Made with Cursor

Record that documentation lands on master and that Read the Docs stable
should track release tags such as v2.1.0.

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

cursor Bot commented Jul 28, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@jepegit
jepegit merged commit ebb69f8 into master Jul 28, 2026
4 checks passed
@jepegit
jepegit deleted the 768-retire-v2-docs-stable branch July 28, 2026 17:56
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