Skip to content

RELEASE: Releasing 12 package(s) (main) - #16361

Merged
Vladimir Morozov (vmoroz) merged 1 commit into
mainfrom
prepare-release/main
Aug 21, 2026
Merged

RELEASE: Releasing 12 package(s) (main)#16361
Vladimir Morozov (vmoroz) merged 1 commit into
mainfrom
prepare-release/main

Conversation

@azure-pipelines

@azure-pipelines azure-pipelines Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

This PR was auto-generated by prepare-release. When ready to release, merge this PR into main. If not ready yet, this PR will be updated as more changes merge.

Packages to Release (12)

@react-native-windows/automation@0.0.0-canary.1059

  • Bump @react-native-windows/automation-channel to v0.0.0-canary.1059

@react-native-windows/automation-channel@0.0.0-canary.1059

  • Fix CI pipeline and add warm-feed
  • Bump react-native-windows to v0.0.0-canary.1059

@react-native-windows/automation-commands@0.0.0-canary.1060

  • Bump @react-native-windows/automation-channel to v0.0.0-canary.1059

@react-native-windows/cli@0.0.0-canary.293

  • Fix CI pipeline and add warm-feed

@react-native-windows/tester@0.0.1

  • Bump react-native-windows to v0.0.0-canary.494

@rnw-scripts/debug-test@0.0.0

  • Bump @react-native-windows/automation to v0.3.14

@rnw-scripts/e2e-test-app-fabric@0.0.0

  • (dependency update)

@rnw-scripts/playground@0.0.54

  • Bump react-native-windows to v0.0.0-canary.494

@rnw-scripts/sample-app-fabric@0.0.1

  • (dependency update)

@rnw-scripts/sample-custom-component@0.0.1

  • (dependency update)

react-native-windows@0.0.0-canary.1059

  • Fix CI pipeline and add warm-feed
  • Release/CI pipeline updates + feed warm-up
  • Null-check the capturing component view before notifying OnPointerCaptureLost (crash when the capturing component was unmounted)
  • Fix(fabric): dispatch touch/pen contacts with the W3C primary button (button 0, buttons 1) instead of button -1 / buttons 0, so pointer-event-driven press handling responds to finger taps the same as mouse left-clicks
  • Bump @react-native-windows/cli to v0.0.0-canary.293

react-native-windows-init@0.0.0-canary.1030

  • Bump @react-native-windows/cli to v0.0.0-canary.293

Copilot AI balanced review requested due to automatic review settings August 10, 2026 16:48
@azure-pipelines
azure-pipelines Bot requested a review from a team as a code owner August 10, 2026 16:48
@azure-pipelines

Copy link
Copy Markdown
Contributor Author
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.

Updates React Native Windows canary versions across the repo and refreshes the generated release artifacts to match the new prerelease.

Changes:

  • Bump react-native-windows canary version from 0.0.0-canary.1058 to 0.0.0-canary.1059 across packages and lockfile.
  • Bump @react-native-windows/automation-* package versions/dependencies (incl. automation-commands to 0.0.0-canary.1060).
  • Regenerate changelogs / version metadata and remove the consumed change file.

Reviewed changes

Copilot reviewed 19 out of 21 changed files in this pull request and generated no comments.

Show a summary per file
File Description
yarn.lock Updates pinned canary versions for react-native-windows and automation packages.
vnext/package.json Bumps react-native-windows package version to 0.0.0-canary.1059.
vnext/PropertySheets/Generated/PackageVersion.g.props Updates MSBuild version + commit ID to match the new canary.
vnext/CHANGELOG.md Adds 0.0.0-canary.1059 entry and updates generated timestamp.
vnext/CHANGELOG.json Adds 0.0.0-canary.1059 entry with associated metadata.
packages/sample-custom-component/package.json Bumps dependency on react-native-windows to ^0.0.0-canary.1059.
packages/sample-app-fabric/package.json Bumps dependency on react-native-windows to ^0.0.0-canary.1059.
packages/playground/package.json Bumps dependency on react-native-windows to ^0.0.0-canary.1059.
packages/e2e-test-app-fabric/package.json Bumps react-native-windows + automation deps to new canary versions.
packages/debug-test/package.json Bumps @react-native-windows/automation to 0.0.0-canary.1059.
packages/@react-native-windows/tester/package.json Bumps dependency/peer dependency on react-native-windows to ^0.0.0-canary.1059.
packages/@react-native-windows/automation/package.json Bumps package version and automation-channel dependency to 0.0.0-canary.1059.
packages/@react-native-windows/automation/CHANGELOG.md Adds 0.0.0-canary.1059 entry and updates generated timestamp.
packages/@react-native-windows/automation/CHANGELOG.json Adds 0.0.0-canary.1059 entry with associated metadata.
packages/@react-native-windows/automation-commands/package.json Bumps package version to 0.0.0-canary.1060 and updates automation-channel dep.
packages/@react-native-windows/automation-commands/CHANGELOG.md Adds 0.0.0-canary.1060 entry and updates generated timestamp.
packages/@react-native-windows/automation-commands/CHANGELOG.json Adds 0.0.0-canary.1060 entry with associated metadata.
packages/@react-native-windows/automation-channel/package.json Bumps package version and react-native-windows devDependency to 0.0.0-canary.1059.
packages/@react-native-windows/automation-channel/CHANGELOG.md Adds 0.0.0-canary.1059 entry and updates generated timestamp.
packages/@react-native-windows/automation-channel/CHANGELOG.json Adds 0.0.0-canary.1059 entry with associated metadata.
change/react-native-windows-0d3e0585-cf54-41f6-b2a4-95b876015aad.json Removes the change file after changelog generation/version bump.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Copilot AI review requested due to automatic review settings August 10, 2026 19:01
@azure-pipelines
azure-pipelines Bot force-pushed the prepare-release/main branch from 0319d8d to 3e6c5c4 Compare August 10, 2026 19:01

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 23 changed files in this pull request and generated no new comments.

Suppressed comments (1)

vnext/CHANGELOG.json:1

  • The last two changelog items reference the same commit hash, but they appear to be distinct changes (and one was sourced from a different change/*.json file). If these are different underlying commits, update/regenerate the changelog so each entry points at the correct commit; otherwise consumers following the commit link will be misled.

Copilot AI review requested due to automatic review settings August 10, 2026 19:03
@azure-pipelines
azure-pipelines Bot force-pushed the prepare-release/main branch from 3e6c5c4 to 9c8ed96 Compare August 10, 2026 19:03

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 23 changed files in this pull request and generated no new comments.

Copilot AI review requested due to automatic review settings August 12, 2026 21:11
@azure-pipelines
azure-pipelines Bot force-pushed the prepare-release/main branch from 9c8ed96 to fe9747a Compare August 12, 2026 21:11

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 23 changed files in this pull request and generated no new comments.

Copilot AI review requested due to automatic review settings August 18, 2026 22:09
@azure-pipelines
azure-pipelines Bot force-pushed the prepare-release/main branch from fe9747a to 343b5af Compare August 18, 2026 22:09

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 23 changed files in this pull request and generated no new comments.

Suppressed comments (3)

packages/@react-native-windows/automation/CHANGELOG.json:14

  • The new changelog entry sets commit to the string "not available", which is not a commit SHA and can break tooling that expects commit to be a valid hash (or absent/null). Consider omitting the commit field when unknown, using null, or populating it with the actual commit SHA used for this release.
            "author": "beachball",
            "package": "@react-native-windows/automation",
            "comment": "Bump @react-native-windows/automation-channel to v0.0.0-canary.1059",
            "commit": "not available"

packages/@react-native-windows/automation-commands/CHANGELOG.json:14

  • Same issue as above: commit is set to "not available" rather than a commit SHA (or being omitted/null). If any consumers parse this field as a git hash, this will cause failures; prefer removing the field or providing a real SHA.
            "author": "beachball",
            "package": "@react-native-windows/automation-commands",
            "comment": "Bump @react-native-windows/automation-channel to v0.0.0-canary.1059",
            "commit": "not available"

packages/@react-native-windows/automation-channel/CHANGELOG.json:14

  • Same issue: the commit value "not available" is not a valid commit identifier. To keep the changelog JSON schema/tooling-friendly, prefer omitting commit, using null, or populating a real commit SHA.
            "author": "beachball",
            "package": "@react-native-windows/automation-channel",
            "comment": "Bump react-native-windows to v0.0.0-canary.1059",
            "commit": "not available"

@vmoroz

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Contributor Author
Azure Pipelines:
Successfully started running 1 pipeline(s).

@vmoroz
Vladimir Morozov (vmoroz) enabled auto-merge (squash) August 18, 2026 22:47
@azure-pipelines
azure-pipelines Bot force-pushed the prepare-release/main branch from 343b5af to ccdfce4 Compare August 20, 2026 11:16
@azure-pipelines azure-pipelines Bot changed the title RELEASE: Releasing 10 package(s) (main) RELEASE: Releasing 12 package(s) (main) Aug 20, 2026
Copilot AI review requested due to automatic review settings August 20, 2026 11:16

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 30 out of 32 changed files in this pull request and generated no new comments.

Suppressed comments (3)

packages/@react-native-windows/tester/package.json:23

  • The generated release description says @react-native-windows/tester is being updated to RNW 0.0.0-canary.494, but this manifest updates it to 0.0.0-canary.1059. prepare-release has reused this private package's 2022 changelog entry because its package version remains 0.0.1; please correct the release summary (and ideally make the generator label unchanged-version private packages as dependency updates).
    "react-native-windows": "^0.0.0-canary.1059",

packages/debug-test/package.json:11

  • The generated release description reports a bump to @react-native-windows/automation@0.3.14, while this change actually selects 0.0.0-canary.1059. The summary is pulling the private package's stale 2022 changelog entry; please correct the release description or update prepare-release to report this as the current dependency update.
    "@react-native-windows/automation": "0.0.0-canary.1059",

packages/playground/package.json:20

  • The generated release description says Playground is updated to RNW 0.0.0-canary.494, but this line updates it to 0.0.0-canary.1059. This comes from reusing the unchanged private package's 2022 changelog entry; please correct the release summary or have prepare-release emit the actual dependency update.
    "react-native-windows": "^0.0.0-canary.1059"

@vmoroz

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Contributor Author
Azure Pipelines:
Successfully started running 1 pipeline(s).

Copilot AI review requested due to automatic review settings August 21, 2026 00:43
@azure-pipelines
azure-pipelines Bot force-pushed the prepare-release/main branch from ccdfce4 to 1e15056 Compare August 21, 2026 00:43

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 30 out of 32 changed files in this pull request and generated no new comments.

Suppressed comments (3)

packages/@react-native-windows/tester/package.json:23

  • The PR description says this package is being updated to react-native-windows@0.0.0-canary.494, but the manifest actually selects 0.0.0-canary.1059. Correct the release summary so it accurately describes the dependency being validated in this release.
    "react-native-windows": "^0.0.0-canary.1059",

packages/debug-test/package.json:11

  • The PR description reports an update to @react-native-windows/automation@0.3.14, while this change selects 0.0.0-canary.1059. Correct the release summary so release reviewers see the dependency version this package will actually use.
    "@react-native-windows/automation": "0.0.0-canary.1059",

packages/playground/package.json:20

  • The PR description says this dependency is moving to react-native-windows@0.0.0-canary.494, but the manifest moves it to 0.0.0-canary.1059. Correct the release summary to match the release contents.
    "react-native-windows": "^0.0.0-canary.1059"

Copilot AI review requested due to automatic review settings August 21, 2026 16:21
@azure-pipelines
azure-pipelines Bot force-pushed the prepare-release/main branch from 1e15056 to 7bec9f0 Compare August 21, 2026 16:21

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 30 out of 32 changed files in this pull request and generated 3 comments.

"react": "^19.2.3",
"react-native": "0.85.0-nightly-20260303-c26dbe286",
"react-native-windows": "^0.0.0-canary.1058"
"react-native-windows": "^0.0.0-canary.1059"
},
"devDependencies": {
"@react-native-windows/automation": "0.0.0-canary.1058",
"@react-native-windows/automation": "0.0.0-canary.1059",
"react": "19.2.3",
"react-native": "0.85.0-nightly-20260303-c26dbe286",
"react-native-windows": "^0.0.0-canary.1058",
"react-native-windows": "^0.0.0-canary.1059",
Copilot AI review requested due to automatic review settings August 21, 2026 16:35
@azure-pipelines
azure-pipelines Bot force-pushed the prepare-release/main branch from 7bec9f0 to ee41bab Compare August 21, 2026 16:35
@vmoroz

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Contributor Author
Azure Pipelines:
Successfully started running 1 pipeline(s).

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 30 out of 32 changed files in this pull request and generated no new comments.

@vmoroz
Vladimir Morozov (vmoroz) merged commit ba376c9 into main Aug 21, 2026
33 checks passed
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.

3 participants