docs: document branch model and update supported versions#904
Open
robdecker wants to merge 1 commit into
Open
Conversation
- Add "Branch model" section to MAINTAINING.md explaining the roles of main / v2.0 / v1.6 and their Vercel docs subdomain mapping. Includes guidance on where to target a PR based on change type. - Replace stale "Docs" deployment list (v1.6/v1/v0) with the current branch → subdomain mapping. Drop the @todo marker now that the details are filled in. - Update SECURITY.md supported-versions tables for both `next-drupal` and the `next` Drupal module to include 2.x.x.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the active-branch model and corrects two stale sections of project docs.
MAINTAINING.mdmain,v2.0, andv1.6, the Vercel docs subdomain each one drives, and where contributors should target PRs based on change type.v1.6,v1,v0) with the currentmain/v2.0/v1.6→ subdomain mapping. Removes the@TODOmarker since the details are now filled in.SECURITY.md2.x.xto the supported-versions table for bothnext-drupaland thenextDrupal module. The current stable npm release is2.0.1, so 2.x is the active line; 1.x remains supported on thev1.6branch.Test plan
Notes
The
nextDrupal module versioning is assumed to follow the same 1.x/2.x split as the npm package. If the contrib module's release line differs, update that table accordingly.