chore: release v2.25.0

[sunnylqm]

One-shot observable release runner for v2.25.0. It checks out verified master commit 516be8d, prepares and verifies version 2.25.0, builds and runs Node.js 18 compatibility checks, verifies the npm package contents, publishes react-native-update-cli@2.25.0 through the repository's npm OIDC trust, and then creates GitHub Release v2.25.0 targeting that exact master commit.

The workflow is idempotent: an already-published npm version or existing GitHub Release is treated as success. This PR is not intended to be merged; the one-shot workflow remains isolated on the release branch.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Summary by CodeRabbit

• Chores
  • Updated the release process to publish version 2.25.0 from the designated release branch.
  • Added automated package verification and smoke testing before publication.
  • Improved handling of repeated publication attempts to avoid failures when a version is already available.
  • Automated creation of the corresponding GitHub release with bilingual release notes while preventing duplicate releases.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: fa22a81f-4bc3-4c71-8241-25023a5e76c5

📥 Commits

Reviewing files that changed from the base of the PR and between 516be8d and 7e32e36.

📒 Files selected for processing (1)

• .github/workflows/publish.yml

---

📝 Walkthrough

Walkthrough

The release workflow now runs from automation/release-v2.25.0, validates and publishes version 2.25.0, tolerates concurrent npm publication, and creates an idempotent GitHub release with bilingual notes.

Changes

Release automation

Layer / File(s)	Summary
Workflow trigger and version setup .github/workflows/publish.yml	The workflow uses a dedicated branch trigger, writable contents permission, serialized release concurrency, and fixed version 2.25.0 metadata.
Package validation and npm publication .github/workflows/publish.yml	Verification runs export checks and scripts/smoke-lib.js. npm publication checks the registry and handles existing or concurrent versions.
Idempotent GitHub release creation .github/workflows/publish.yml	The workflow creates release v2.25.0 with bilingual notes and the pinned commit. Existing releases are treated as successful.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant GitHub as GitHub Actions
  participant Package as Package checks
  participant Registry as npm registry
  participant Releases as GitHub Releases
  GitHub->>Package: Verify package version and run smoke test
  GitHub->>Registry: Check and publish react-native-update-cli@2.25.0
  Registry-->>GitHub: Report publication or existing version
  GitHub->>Releases: Create v2.25.0 with bilingual release notes
  Releases-->>GitHub: Create release or report existing release

Loading

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch automation/release-v2.25.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sunnylqm]

Release completed successfully from verified master commit 516be8d788239e4d74e5bb81d5f03ca0adcd4a8c.

• Published react-native-update-cli@2.25.0 to npm with GitHub Actions provenance.
• Created GitHub Release v2.25.0 targeting the same master commit.
• Build, package inspection, Node.js 18.17 runtime checks, CLI smoke tests, and proxy smoke tests all passed.

This one-shot release PR is being closed without merge, as intended.