RELEASE: Releasing 15 package(s) (main) - #16399
Open
azure-pipelines[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Prepares 15 React Native Windows packages for release after the React Native 0.86 nightly integration.
Changes:
- Increments canary package versions and dependency references.
- Updates generated changelogs and native package metadata.
- Refreshes the lockfile and consumes release change files.
Reviewed changes
Copilot reviewed 37 out of 39 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
yarn.lock |
Synchronizes workspace dependency versions. |
vnext/PropertySheets/Generated/PackageVersion.g.props |
Updates native package version metadata. |
vnext/package.json |
Bumps RNW and CLI versions. |
vnext/CHANGELOG.md |
Adds the RNW release entry. |
vnext/CHANGELOG.json |
Adds structured RNW release metadata. |
packages/sample-custom-component/package.json |
Updates its RNW dependency. |
packages/sample-app-fabric/package.json |
Updates its RNW dependency. |
packages/react-native-windows-init/package.json |
Bumps init and CLI versions. |
packages/react-native-windows-init/CHANGELOG.md |
Adds the init release entry. |
packages/react-native-windows-init/CHANGELOG.json |
Adds structured init release metadata. |
packages/playground/package.json |
Updates its RNW dependency. |
packages/e2e-test-app-fabric/package.json |
Updates RNW testing dependencies. |
packages/debug-test/package.json |
Updates the automation dependency. |
packages/@react-native-windows/tester/package.json |
Updates RNW peer and development dependencies. |
packages/@react-native-windows/perf-testing/package.json |
Bumps the performance package version. |
packages/@react-native-windows/perf-testing/CHANGELOG.md |
Adds the performance release entry. |
packages/@react-native-windows/perf-testing/CHANGELOG.json |
Adds structured performance release metadata. |
packages/@react-native-windows/cli/package.json |
Bumps the CLI version. |
packages/@react-native-windows/cli/CHANGELOG.md |
Adds the CLI release entry. |
packages/@react-native-windows/cli/CHANGELOG.json |
Adds structured CLI release metadata. |
packages/@react-native-windows/automation/package.json |
Bumps automation and channel versions. |
packages/@react-native-windows/automation/CHANGELOG.md |
Adds the automation release entry. |
packages/@react-native-windows/automation/CHANGELOG.json |
Adds structured automation release metadata. |
packages/@react-native-windows/automation-commands/package.json |
Bumps commands and channel versions. |
packages/@react-native-windows/automation-commands/CHANGELOG.md |
Adds the commands release entry. |
packages/@react-native-windows/automation-commands/CHANGELOG.json |
Adds structured commands release metadata. |
packages/@react-native-windows/automation-channel/package.json |
Bumps channel and RNW versions. |
packages/@react-native-windows/automation-channel/CHANGELOG.md |
Adds the channel release entry. |
packages/@react-native-windows/automation-channel/CHANGELOG.json |
Adds structured channel release metadata. |
packages/@office-iss/react-native-win32/package.json |
Bumps the Win32 package version. |
packages/@office-iss/react-native-win32/CHANGELOG.md |
Adds the Win32 release entry. |
packages/@office-iss/react-native-win32/CHANGELOG.json |
Adds structured Win32 release metadata. |
packages/@office-iss/react-native-win32-tester/package.json |
Updates Win32 peer and development dependencies. |
change/react-native-windows-init-53ef3775-da45-4571-b19b-dc779c19e5cc.json |
Consumes the init change file. |
change/react-native-windows-425fdab2-f5eb-4834-8a89-ee086d4bbcc2.json |
Consumes the RNW change file. |
change/@react-native-windows-perf-testing-33791a23-ae76-4ba0-bf50-49a940d870e8.json |
Consumes the performance change file. |
change/@react-native-windows-cli-66f8bb72-2223-4893-8a6a-2ab820ac0e0f.json |
Consumes the CLI change file. |
change/@react-native-windows-automation-channel-58609dc1-dbb5-4bbe-9521-41be4bf14e9c.json |
Consumes the channel change file. |
change/@office-iss-react-native-win32-851c2fb9-e545-430b-bbf9-bcc1431006f0.json |
Consumes the Win32 change file. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
azure-pipelines
Bot
force-pushed
the
prepare-release/main
branch
from
August 24, 2026 22:46
1ea713f to
9ce38b8
Compare
azure-pipelines
Bot
force-pushed
the
prepare-release/main
branch
from
August 25, 2026 20:42
9ce38b8 to
8e181fd
Compare
| }, | ||
| "peerDependencies": { | ||
| "@office-iss/react-native-win32": "^0.0.0-canary.312", | ||
| "@office-iss/react-native-win32": "^0.0.0-canary.313", |
| "react": "19.2.3", | ||
| "react-native": "0.86.0-nightly-20260310-621592d1f", | ||
| "react-native-windows": "^0.0.0-canary.1060", | ||
| "react-native-windows": "^0.0.0-canary.1061", |
| "react": "^19.2.3", | ||
| "react-native": "0.86.0-nightly-20260310-621592d1f", | ||
| "react-native-windows": "^0.0.0-canary.1060" | ||
| "react-native-windows": "^0.0.0-canary.1061" |
| }, | ||
| "devDependencies": { | ||
| "@react-native-windows/automation": "0.0.0-canary.1060", | ||
| "@react-native-windows/automation": "0.0.0-canary.1061", |
azure-pipelines
Bot
force-pushed
the
prepare-release/main
branch
from
August 26, 2026 02:41
8e181fd to
6f536b5
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 43 out of 45 changed files in this pull request and generated no new comments.
Suppressed comments (1)
packages/@react-native-windows/tester/package.json:23
- The PR description reports stale release notes for the private workspaces: this dependency is described as
react-native-windows@0.0.0-canary.494, but the artifact actually updates it to0.0.0-canary.1061. The same mismatch appears for win32-tester (.147vs.313), debug-test (0.3.14vs.1061), and playground (.494vs.1061), apparently because their latest changelogs date from 2022. Regenerate or correct the release description from the current dependency changes so the stated release contents match what will be merged.
azure-pipelines
Bot
force-pushed
the
prepare-release/main
branch
from
August 27, 2026 22:18
6f536b5 to
0453f5a
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 44 out of 46 changed files in this pull request and generated no new comments.
Suppressed comments (4)
packages/@office-iss/react-native-win32-tester/package.json:20
- The generated release description says this package bumps
@office-iss/react-native-win32to canary.147 (and lists two unrelated 2022-era dependency bumps), but this release actually moves it to canary.313. Regenerate or correct the release description so reviewers and release operators see the dependencies being shipped.
"@office-iss/react-native-win32": "^0.0.0-canary.313",
packages/@react-native-windows/tester/package.json:23
- The release description reports a bump to
react-native-windowscanary.494, whereas this release changes the dependency to canary.1061. Update the generated description so it reflects the artifact being reviewed.
packages/playground/package.json:20 - The release description lists a
react-native-windowscanary.494 bump for Playground, while this line updates it to canary.1061. Regenerate or edit the description so the release summary matches the dependency update.
packages/debug-test/package.json:11 - The release description claims this dependency is being bumped to
@react-native-windows/automation0.3.14, but the actual change is to canary.1061. Correct or regenerate the description to avoid publishing an inaccurate release plan.
azure-pipelines
Bot
force-pushed
the
prepare-release/main
branch
from
August 30, 2026 23:22
0453f5a to
594a23c
Compare
azure-pipelines
Bot
force-pushed
the
prepare-release/main
branch
from
August 31, 2026 23:06
594a23c to
ee91b95
Compare
azure-pipelines
Bot
force-pushed
the
prepare-release/main
branch
from
September 1, 2026 21:24
ee91b95 to
68c9611
Compare
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Several package entries in the generated release description report stale dependency versions that do not match the manifests.
Review details
Suppressed comments (4)
packages/@office-iss/react-native-win32-tester/package.json:20
- The PR description says this package bumps
@office-iss/react-native-win32to0.0.0-canary.147(and lists two unrelated dependency bumps), but this release actually changes it to0.0.0-canary.313. Update the release summary so reviewers and release automation are not given stale package contents.
"@office-iss/react-native-win32": "^0.0.0-canary.313",
packages/@react-native-windows/tester/package.json:23
- The PR description reports a bump to
react-native-windows@0.0.0-canary.494, while this release updates the dependency to0.0.0-canary.1061. Correct the package entry in the release summary so it describes the artifact being reviewed.
packages/debug-test/package.json:11 - The PR description claims this package bumps automation to
0.3.14, but the actual dependency is0.0.0-canary.1061. Update the release summary to the current version before using it to approve the release.
packages/playground/package.json:20 - The PR description says Playground bumps
react-native-windowsto0.0.0-canary.494, whereas this dependency is being updated to0.0.0-canary.1061. Correct the release summary so it does not present stale release contents.
- Files reviewed: 53/55 changed files
- Comments generated: 0 new
- Review effort level: Balanced
azure-pipelines
Bot
force-pushed
the
prepare-release/main
branch
from
September 1, 2026 23:02
68c9611 to
2f3dacf
Compare
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
The generated PR description reports several stale dependency versions that contradict the release manifests and lockfile.
Review details
Suppressed comments (1)
packages/@react-native-windows/tester/package.json:23
- The PR description says this dependency is being bumped to
canary.494, but the manifest and lockfile actually selectcanary.1061. The description similarly reports stale 2022-era versions forreact-native-win32-tester,debug-test, andplayground, so release reviewers cannot rely on its package summary. Please regenerate or correct the PR body to list the dependency versions actually changed here.
- Files reviewed: 54/56 changed files
- Comments generated: 0 new
- Review effort level: Balanced
azure-pipelines
Bot
force-pushed
the
prepare-release/main
branch
from
September 1, 2026 23:17
2f3dacf to
b645d1f
Compare
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Four release-summary entries report stale dependency versions instead of those in the updated manifests.
Review details
Suppressed comments (4)
packages/@office-iss/react-native-win32-tester/package.json:20
- The PR description says this package bumps
@office-iss/react-native-win32to.147(and lists old eslint/override bumps), but this release actually moves both references to.313. Those notes come from the package's 2022 changelog and do not describe this dependency update; please correct or regenerate the PR body from the current diff.
"@office-iss/react-native-win32": "^0.0.0-canary.313",
packages/@react-native-windows/tester/package.json:23
- The PR description reports a bump to
react-native-windows@0.0.0-canary.494, while this package is actually being updated to.1061. Please correct or regenerate the release notes so they identify the dependency version that will be tested by this PR.
packages/playground/package.json:20 - The PR description claims the playground bump targets
react-native-windows@0.0.0-canary.494, but this change targets.1061. Please update the release summary to reflect the dependency version in the generated manifest.
packages/debug-test/package.json:11 - The PR description says
debug-testis being updated to@react-native-windows/automation@0.3.14, but this line updates it to0.0.0-canary.1061. Please replace the stale changelog note in the PR body with the actual dependency update.
- Files reviewed: 54/56 changed files
- Comments generated: 0 new
- Review effort level: Balanced
azure-pipelines
Bot
force-pushed
the
prepare-release/main
branch
from
September 5, 2026 02:49
b645d1f to
bb2f1ca
Compare
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Several generated release-summary entries report stale dependency versions that do not match the manifests.
Review details
Suppressed comments (4)
packages/@react-native-windows/tester/package.json:23
- The generated PR description says this dependency is being bumped to
0.0.0-canary.494, while the actual release diff targets0.0.0-canary.1061. Please regenerate or correct the release summary so approvers are not validating against stale release contents.
packages/debug-test/package.json:11 - The generated PR description reports an automation bump to
v0.3.14, but this dependency is actually updated to0.0.0-canary.1061. Please regenerate or correct the release summary to describe the version being tested by this PR.
packages/playground/package.json:20 - The generated PR description claims this dependency is bumped to
0.0.0-canary.494, whereas the manifest targets0.0.0-canary.1061. Please regenerate or correct the release summary before using it as the release approval record.
packages/@office-iss/react-native-win32-tester/package.json:20 - The generated PR description lists an old
@office-iss/react-native-win32bump to0.0.0-canary.147(plus obsolete tool-version bumps), but this diff targets0.0.0-canary.313. Please regenerate or correct this release-summary entry to match the actual dependencies.
"@office-iss/react-native-win32": "^0.0.0-canary.313",
- Files reviewed: 60/62 changed files
- Comments generated: 0 new
- Review effort level: Balanced
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.
This PR was auto-generated by
prepare-release. When ready to release, merge this PR intomain. If not ready yet, this PR will be updated as more changes merge.Packages to Release (15)
@office-iss/react-native-win32@0.0.0-canary.313
@office-iss/react-native-win32-tester@0.0.1
@react-native-windows/automation@0.0.0-canary.1061
@react-native-windows/automation-channel@0.0.0-canary.1061
@react-native-windows/automation-commands@0.0.0-canary.1062
@react-native-windows/cli@0.0.0-canary.294
@react-native-windows/perf-testing@0.0.0-canary.1040
@react-native-windows/tester@0.0.1
@rnw-scripts/debug-test@0.0.0
@rnw-scripts/e2e-test-app-fabric@0.0.0
@rnw-scripts/playground@0.0.54
@rnw-scripts/sample-app-fabric@0.0.1
@rnw-scripts/sample-custom-component@0.0.1
react-native-windows@0.0.0-canary.1061
react-native-windows-init@0.0.0-canary.1031