Skip to content

docs: document the main/maintenance/v1 branch split and release steps#55

Closed
toiroakr wants to merge 2 commits into
mainfrom
docs/branch-split-notes
Closed

docs: document the main/maintenance/v1 branch split and release steps#55
toiroakr wants to merge 2 commits into
mainfrom
docs/branch-split-notes

Conversation

@toiroakr

Copy link
Copy Markdown
Contributor

Summary

  • Document in CLAUDE.md that main is now the v2 line (tailor CLI) and
    maintenance/v1 holds the pre-rename v1 line (tailor-sdk CLI), including how to
    target a release at maintenance/v1 with gh release create --target.
  • Add a short "Versioning" section to README.md pointing users at the @v2/@v1
    major tags and the maintenance/v1 branch.

toiroakr added 2 commits July 22, 2026 21:17
Explain in CLAUDE.md that main is now the v2 line (tailor CLI) and
maintenance/v1 holds the pre-rename v1 line (tailor-sdk CLI) for
patch releases, including how to target it with gh release create
--target. Add a short Versioning section to README.md pointing users
at the v2/v1 major tags and the maintenance/v1 branch.
maintenance/v1 gets the same branch protection as main, not the
direct-push workflow the previous commit described.
@toiroakr

Copy link
Copy Markdown
Contributor Author

Superseded by #57, which now targets main directly and includes everything from this PR plus the Changesets release automation.

@toiroakr toiroakr closed this Jul 22, 2026
@toiroakr
toiroakr deleted the docs/branch-split-notes branch July 22, 2026 12:57
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