rive-app / rive-app/rive-react-native
Version bump script needs tweaking
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 783
- Forks
- 81
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 3
Description
If we manually bump the version in package.json for the next release, (i.e a major version), the patch version does not change back to 0 as expected, and will still increment from the previous patch version.
i.e 2.1.37 -> 3.0.0 actually releases 3.0.28.
Need to check into the GH workflow scripts to figure out how to properly reset these semver numbers.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with package.json and the GitHub workflow scripts responsible for version bumps. Reproduce the major-version case described in the issue, then verify that changing 2.1.37 to the next major release produces 3.0.0 rather than retaining the previous patch number.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100