-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(lerna): aggressive patch bump #1163
base: release-v10
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Im not too familiar with this setup, but from what I see, it seems like this changes a bit of the release logic. We should then also update the
CONTRIBUTING Readme
so it mirrors these changes. Both regarding to the logic we should have when we remove
--conventional-commits
The logic around bump-verion etc.
I'm not too opinionated on what the best release strategy is as long as it is well documented
Updated the contributing guidelines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should add some details on how we want to work with release branches. In other repos I have worked with, all fixes are merged into master, and then fixes are cherry picked from master to release branches. We should have some documentation on how we want to do this?
CONTRIBUTING.md
Outdated
@@ -166,72 +172,4 @@ git push && git push --tags | |||
``` | |||
|
|||
This will make a commit with the updated `package.json`, create a new git tag, and publish to npm. | |||
Make sure you are logged in to npm, talk to a maintainer. | |||
|
|||
## Code overview |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why the "Code overview" section is removed in the PR?
if [[ "${GITHUB_REF}" == "refs/heads/master" ]]; then | ||
EVENT_PATH_CONTENT=$(cat ${GITHUB_EVENT_PATH} | jq -r '.') | ||
HEAD_COMMIT_MSG=$(echo $EVENT_PATH_CONTENT | jq -r '.head_commit.message') | ||
MERGE_COMMIT_MSG=$(echo $EVENT_PATH_CONTENT | jq -r '.commits[-1].message') | ||
|
||
if [[ "$HEAD_COMMIT_MSG" == *"Merge"* && "$HEAD_COMMIT_MSG" == *"release-"* && "$HEAD_COMMIT_MSG" == *"[release]"* ]] || | ||
[[ "$MERGE_COMMIT_MSG" == *"Merge"* && "$MERGE_COMMIT_MSG" == *"release-"* && "$MERGE_COMMIT_MSG" == *"[release]"* ]]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These checks are a bit hard to read. What's the intention?
scripts/remove-rc-tags.js
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
Addressing Lerna aggressive versioning
References
Modifications made