[CI] Add another step to update `package.json` version number
Open
@nebula-aac is already working on this.
Since Aug 14, 2024.
area/ci
follow-up
issue/willfix
- Dominant language
- TypeScript
- Stars
- 137
- Forks
- 239
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 5
Description
After adding reedyuk/npm-version@1.1.1 to set package version, the version did not change in package.json at all, which still requires a manual step or add another step in the workflow in order to make sure that the package.json stays sync with the GitHub Release.
Contributor Guides and Resources
- 🛠 Meshery Build & Release Strategy
- 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
- 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack
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.
Assessment
This issue has not been assessed yet.