-
Notifications
You must be signed in to change notification settings - Fork 39
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
chore: release scripts for travis #54
Conversation
bin/ci-release.sh
Outdated
# CANARY RELEASE WITH COMMIT NAME | ||
# @commit | ||
yarn install && \ | ||
yarn lerna publish --skip-git --skip-npm --exact --force-publish=* --canary=commit --registry http://localhost:4873/ |
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.
localhost:4873 ?
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 it's verdaccio's URL .
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.
true, I forgot to change that one
Add CLI tools/helpers for releasing. Add peer dependency update util. Add npm release for @next and @canary releases.
836ef82
to
e574442
Compare
This is ready for the review. @ayusharma please feel free to jump in and comment. |
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.
note to self: Don't forget to add CHANGELOG
bin/ci-release.sh
Outdated
if [ "$TRAVIS_BRANCH" = "master" ]; then | ||
# RELEASE AS @NEXT | ||
yarn install && \ | ||
yarn lerna publish --skip-git --exact --force-publish=* --canary=commit --npm-tag=next --registry https://registry.npmjs.org |
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 am not sure about --exact
. There is nothing mentioned in docs https://lernajs.io/#command-publish
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.
Melody uses 2.x version of Lerna still. https://github.com/lerna/lerna/tree/2.x#--exact
} | ||
|
||
Object.keys(pkgJson.peerDependencies).forEach(dep => { | ||
if (pkgNames.indexOf(dep) > -1) { |
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.
Better to use .includes
. 😄
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 tested it locally. Added scripts work fine. Looks good to me :)
@efegurkan Can we get the automated tests to pass? |
|
@pago It's a bug. May be |
@pago can be also bundlesize token bound to my account? Does it fail on other PR's as well. In that case you need to renew the token. |
@efegurkan , @pago , I added PR #63 that updates |
@frvge ask someone to add you to the github organization. You should be able to add the tokens. I cannot work on this PR anymore you know 🤷♂️ :D |
#65) * chore: Update bundlesize, add secret token, remove npm and lerna warnings * chore: Force non-interactive 'yes' for lerna publish
Almost there. I'm not sure why but the npm website currently doesn't list Once that is done, travis should pass, leaving us with the broken circleci tests on node 6. |
Reference issue: N/A
This PR adds changes to the release scripts and travis config to enable testing melody easier and more flexible at trivago.
With this changes, every push to the master should release a new version to the
@next
tag with next minor version + commit id. Also for the any branch push it should create a release to the@canary
tag.This also includes a tiny peer dependency updating utility and some prompts before releasing. That should prevent unnecessary patch releases in future.