Add automated release scripts #3784
Merged
Conversation
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
m-bert
reviewed
Oct 28, 2025
m-bert
reviewed
Oct 30, 2025
m-bert
approved these changes
Oct 30, 2025
akwasniewski
approved these changes
Oct 30, 2025
m-bert
approved these changes
Oct 30, 2025
Contributor
m-bert
left a comment
m-bert
left a comment
There was a problem hiding this comment.
Should be fine, remember to change workflow in npm settings 😅
j-piasecki
added a commit
that referenced
this pull request
Oct 30, 2025
## Description #3784 added new release scripts, but there was a leftover workflow for releasing a commitly. This PR gets rid of it. I also noticed that the `homepage` field in package.json points to our readme instead of the docs, so I changed that. Finally, I added `paths` filter to the release workflow, so changes only affecting docs, example apps, or scripts won't trigger a release. ## Test plan The failed job got removed. As for the other change - https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#onpushpull_requestpull_request_targetpathspaths-ignore. > If you define both branches/branches-ignore and paths/paths-ignore, the workflow will only run when both filters are satisfied.
j-piasecki
added a commit
that referenced
this pull request
Nov 3, 2025
## Description Implements automated release scripts for the repository. A new nightly release should be triggered on every commit pushed to the `main` branch. Version resolution happens automatically - the `latest` tag is pulled from npm, 1 is added to the minor, and the patch is set to 0. The full version is `$major.$minor$.$patch-$year$month$day-$sha`. To release a stable version, cut a branch with the name matching format of `$major.$minor-stable` and trigger the `publish-stable-release` on that branch. By default, it does a dry run, skipping publishing the package and committing changes. Use that to make sure everything is correct before an actual release. It also uploads the package that would've been published as a GitHub artifact, which could be useful for testing. Version resolution happens automatically: - the major and minor are inferred from the branch name - next patch name is figured out from npm, in the dumbest possible way - iteratively check the patch versions until a not-released one is found - if the minor is exactly +1 compared to the latest and the patch is 0 or the minor matches the latest and the patch is +1, the release is tagged as latest In the future, we may want to run static checks automatically and app builds before releasing, but that would require refactoring our CI to rely more on reusable workflows. ## Test plan Tested on a fork. Release commitly run: https://github.com/j-piasecki/react-native-gesture-handler/actions/runs/18902148546/job/53951686147 (failed on publish due to missing provenance) Release stable run for existing version: https://github.com/j-piasecki/react-native-gesture-handler/actions/runs/18902287389/job/53952137361 (this one succeeded because I commented out `npm publish` and replaced it with `echo`) And here is the created release commit: j-piasecki@211296a. You can notice that the tag was also created successfully. Release stable run for a new version: https://github.com/j-piasecki/react-native-gesture-handler/actions/runs/18903154587/job/53954932559 (this one was a dry run).
j-piasecki
added a commit
that referenced
this pull request
Nov 3, 2025
## Description #3784 added new release scripts, but there was a leftover workflow for releasing a commitly. This PR gets rid of it. I also noticed that the `homepage` field in package.json points to our readme instead of the docs, so I changed that. Finally, I added `paths` filter to the release workflow, so changes only affecting docs, example apps, or scripts won't trigger a release. ## Test plan The failed job got removed. As for the other change - https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#onpushpull_requestpull_request_targetpathspaths-ignore. > If you define both branches/branches-ignore and paths/paths-ignore, the workflow will only run when both filters are satisfied.
j-piasecki
added a commit
that referenced
this pull request
Nov 20, 2025
## Description Implements automated release scripts for the repository. A new nightly release should be triggered on every commit pushed to the `main` branch. Version resolution happens automatically - the `latest` tag is pulled from npm, 1 is added to the minor, and the patch is set to 0. The full version is `$major.$minor$.$patch-$year$month$day-$sha`. To release a stable version, cut a branch with the name matching format of `$major.$minor-stable` and trigger the `publish-stable-release` on that branch. By default, it does a dry run, skipping publishing the package and committing changes. Use that to make sure everything is correct before an actual release. It also uploads the package that would've been published as a GitHub artifact, which could be useful for testing. Version resolution happens automatically: - the major and minor are inferred from the branch name - next patch name is figured out from npm, in the dumbest possible way - iteratively check the patch versions until a not-released one is found - if the minor is exactly +1 compared to the latest and the patch is 0 or the minor matches the latest and the patch is +1, the release is tagged as latest In the future, we may want to run static checks automatically and app builds before releasing, but that would require refactoring our CI to rely more on reusable workflows. ## Test plan Tested on a fork. Release commitly run: https://github.com/j-piasecki/react-native-gesture-handler/actions/runs/18902148546/job/53951686147 (failed on publish due to missing provenance) Release stable run for existing version: https://github.com/j-piasecki/react-native-gesture-handler/actions/runs/18902287389/job/53952137361 (this one succeeded because I commented out `npm publish` and replaced it with `echo`) And here is the created release commit: j-piasecki@211296a. You can notice that the tag was also created successfully. Release stable run for a new version: https://github.com/j-piasecki/react-native-gesture-handler/actions/runs/18903154587/job/53954932559 (this one was a dry run).
j-piasecki
added a commit
that referenced
this pull request
Nov 20, 2025
## Description #3784 added new release scripts, but there was a leftover workflow for releasing a commitly. This PR gets rid of it. I also noticed that the `homepage` field in package.json points to our readme instead of the docs, so I changed that. Finally, I added `paths` filter to the release workflow, so changes only affecting docs, example apps, or scripts won't trigger a release. ## Test plan The failed job got removed. As for the other change - https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#onpushpull_requestpull_request_targetpathspaths-ignore. > If you define both branches/branches-ignore and paths/paths-ignore, the workflow will only run when both filters are satisfied.
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.
Description
Implements automated release scripts for the repository.
A new nightly release should be triggered on every commit pushed to the
mainbranch. Version resolution happens automatically - thelatesttag is pulled from npm, 1 is added to the minor, and the patch is set to 0. The full version is$major.$minor$.$patch-$year$month$day-$sha.To release a stable version, cut a branch with the name matching format of
$major.$minor-stableand trigger thepublish-stable-releaseon that branch. By default, it does a dry run, skipping publishing the package and committing changes. Use that to make sure everything is correct before an actual release. It also uploads the package that would've been published as a GitHub artifact, which could be useful for testing. Version resolution happens automatically:In the future, we may want to run static checks automatically and app builds before releasing, but that would require refactoring our CI to rely more on reusable workflows.
Test plan
Tested on a fork.
Release commitly run: https://github.com/j-piasecki/react-native-gesture-handler/actions/runs/18902148546/job/53951686147 (failed on publish due to missing provenance)
Release stable run for existing version: https://github.com/j-piasecki/react-native-gesture-handler/actions/runs/18902287389/job/53952137361 (this one succeeded because I commented out
npm publishand replaced it withecho)And here is the created release commit: j-piasecki@211296a. You can notice that the tag was also created successfully.
Release stable run for a new version: https://github.com/j-piasecki/react-native-gesture-handler/actions/runs/18903154587/job/53954932559 (this one was a dry run).