fix(release script): not updating root package.json version + not supporting some shells (@NadAlaba)
#5825
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
When updating the version, the script is getting current version from root
package.json, but updatingrelease/package.json, so rootpackage.jsonnever gets updated and minor will always be zero.Chosen solution was to get version from root, but update both.
Other possible solution is to not use version in
release/package.jsonat all (i.e, get and set version in root only).[EDIT]
Solution changed to removing version from all
package.jsonother than root one, and only get and update it in root.Change single quotes in

nodemon --exec '...'to double quotes.Changes in
buildChangelog.getLog()are because some shells don't support evaluating subexpressions in$(...).Change root
package.jsonversion to current version.In commit titles, trailing parenthesis that are not usernames or PR numbers are being considered PRs. So now usernames get matched when they start with

@and PRs when they start with#.