Skip to content

chore(publish): fix GH release not containing change logs#2560

Merged
tido64 merged 1 commit into
trunkfrom
tido/fix-release-notes
Sep 15, 2025
Merged

chore(publish): fix GH release not containing change logs#2560
tido64 merged 1 commit into
trunkfrom
tido/fix-release-notes

Conversation

@tido64
Copy link
Copy Markdown
Member

@tido64 tido64 commented Sep 11, 2025

Description

Fixed GH release not containing change logs

Platforms affected

  • Android
  • iOS
  • macOS
  • visionOS
  • Windows

Test plan

Before:

% yarn nx release --dry-run

 NX   Running release version for project: react-native-test-app

react-native-test-app 🏷️  Resolved the current version as 4.4.10 from git tag "4.4.10", based on releaseTagPattern "{version}"
react-native-test-app 📄 Resolved the specifier as "patch" using git history and the conventional commits standard
react-native-test-app ❓ Applied semver relative bump "patch", derived from conventional commits data, to get new version 4.4.11
react-native-test-app ✍️  New version 4.4.11 written to manifest: package.json

UPDATE package.json [dry-run]

    "name": "react-native-test-app",
-   "version": "0.0.1-dev",
+   "version": "4.4.11",
    "description": "react-native-test-app provides a test app for all supported platforms as a package",


 NX   Tagging commit with git


 NX   Pushing to git remote "origin"


 NX   Creating GitHub Release

CREATE https://github.com/microsoft/react-native-test-app/releases/tag/4.4.11 [dry-run]

+ ## 4.4.11 (2025-09-11)
+
+ This was a version bump only for react-native-test-app to align it with other projects, there were no code changes.


 NX   Skipped publishing packages.


NOTE: The "dryRun" flag means no changes were made.

After:

% yarn nx release --dry-run

 NX   Running release version for project: react-native-test-app

react-native-test-app 🏷️  Resolved the current version as 4.4.10 from git tag "4.4.10", based on releaseTagPattern "{version}"
react-native-test-app 📄 Resolved the specifier as "patch" using git history and the conventional commits standard
react-native-test-app ❓ Applied semver relative bump "patch", derived from conventional commits data, to get new version 4.4.11
react-native-test-app ✍️  New version 4.4.11 written to manifest: package.json

UPDATE package.json [dry-run]

    "name": "react-native-test-app",
-   "version": "0.0.1-dev",
+   "version": "4.4.11",
    "description": "react-native-test-app provides a test app for all supported platforms as a package",


 NX   Tagging commit with git


 NX   Pushing to git remote "origin"


 NX   Creating GitHub Release

CREATE https://github.com/microsoft/react-native-test-app/releases/tag/4.4.11 [dry-run]

+ ## 4.4.11 (2025-09-11)
+
+ ### 🩹 Fixes
+
+ - **windows:** include New Arch build in `test:matrix` ([827bbcfe](https://github.com/microsoft/react-native-test-app/commit/827bbcfe))


 NX   Skipped publishing packages.


NOTE: The "dryRun" flag means no changes were made.

@tido64 tido64 requested a review from Saadnajmi September 11, 2025 07:40
@tido64 tido64 requested a review from JasonVMo as a code owner September 11, 2025 07:40
@tido64 tido64 merged commit 0c2b702 into trunk Sep 15, 2025
30 checks passed
@tido64 tido64 deleted the tido/fix-release-notes branch September 15, 2025 08:05
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