Skip to content

docs: update release process for Changesets - #3032

Merged
Saadnajmi merged 2 commits into
microsoft:mainfrom
Saadnajmi:saadnajmi/release-docs-changesets
Aug 4, 2026
Merged

docs: update release process for Changesets#3032
Saadnajmi merged 2 commits into
microsoft:mainfrom
Saadnajmi:saadnajmi/release-docs-changesets

Conversation

@Saadnajmi

Copy link
Copy Markdown
Collaborator

Summary

  • replace stale Nx Release/version-plan contributor guidance with the current Changesets workflow
  • document pinned-SHA upstream stable syncs, peer updates, Changeset creation and validation, and lock/pod regeneration
  • explain that stable-branch pushes create or update a follow-up Changesets version PR that materializes versions and changelogs

Stale behavior corrected

The documented yarn nx release plan ... command is now a successful no-op because Nx version plans are disabled.
These pages now point contributors to yarn change, yarn change:check, and the active stable-branch Changesets
workflow instead.

Docusaurus versioning assessment

The docsite currently has no versions.json, versioned_docs, or versioned_sidebars. These pages describe the
current contributor and release process rather than version-specific user-facing APIs, so snapshotting them would
freeze stale operational instructions and multiply maintenance. This PR keeps them as current docs and does not add
Docusaurus version snapshots.

Test plan

  • yarn prettier --check docsite/docs/contributing/versioning.md docsite/docs/releases/patch-release.md
  • yarn lint-markdown docsite/docs/contributing/versioning.md docsite/docs/releases/patch-release.md
  • yarn --cwd docsite build
  • yarn --cwd docsite typecheck (currently reports the pre-existing missing @fluentui/react-icons module in the
    unchanged homepage components)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@Saadnajmi
Saadnajmi marked this pull request as ready for review July 29, 2026 21:09
@Saadnajmi
Saadnajmi requested a review from a team as a code owner July 29, 2026 21:09
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: c19d37f3-daaf-41f8-8166-8400a62733f5
@Saadnajmi
Saadnajmi merged commit cc5fac9 into microsoft:main Aug 4, 2026
28 checks passed
Saadnajmi added a commit that referenced this pull request Aug 6, 2026
## Summary

- replace stale Nx Release/version-plan contributor guidance with the
current Changesets workflow
- document pinned-SHA upstream stable syncs, peer updates, Changeset
creation and validation, and lock/pod regeneration
- explain that stable-branch pushes create or update a follow-up
Changesets version PR that materializes versions and changelogs

## Stale behavior corrected

The documented `yarn nx release plan ...` command is now a successful
no-op because Nx version plans are disabled.
These pages now point contributors to `yarn change`, `yarn
change:check`, and the active stable-branch Changesets
workflow instead.

## Docusaurus versioning assessment

The docsite currently has no `versions.json`, `versioned_docs`, or
`versioned_sidebars`. These pages describe the
current contributor and release process rather than version-specific
user-facing APIs, so snapshotting them would
freeze stale operational instructions and multiply maintenance. This PR
keeps them as current docs and does not add
Docusaurus version snapshots.

## Test plan

- `yarn prettier --check docsite/docs/contributing/versioning.md
docsite/docs/releases/patch-release.md`
- `yarn lint-markdown docsite/docs/contributing/versioning.md
docsite/docs/releases/patch-release.md`
- `yarn --cwd docsite build`
- `yarn --cwd docsite typecheck` *(currently reports the pre-existing
missing `@fluentui/react-icons` module in the
  unchanged homepage components)*

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: c19d37f3-daaf-41f8-8166-8400a62733f5
(cherry picked from commit cc5fac9)
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.

2 participants