[CI] Add another step to update `package.json` version number
Opened this issue ยท 2 comments
nebula-aac commented
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
nebula-aac commented
bump, need to follow up on this issue, as the package.json
is at a different version then the released version
nebula-aac commented
bump again