-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
semantic-release setup #1361
semantic-release setup #1361
Conversation
c3c062d
to
21b2048
Compare
the test with Node 4 fails because npm errors if peerDependencies are not fulfilled while npm 3+ only shows a warning. I suggest we add "peerDependencies": {
"hubot": ">=2 <10 || 0.0.0-development"
}, I tested it locally and it worked. I’ll update the evolution process and the PRs that I already sent to the scripts |
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.
Was it intentional to remove the CHANGELOG.md? Should we keep that around for things before semantic-release is used?
@technicalpickles we will add a link to the last version of the |
21b2048
to
6475fc8
Compare
BREAKING CHANGE: [email protected] and [email protected] are no longer supported BREAKING CHANGE: Deep requires like `require(hubot/src/adapter)` are no longer supported, use `require(hubot).Adapter` instead. BREAKING CHANGE: `Middleware.ticker()` has been removed. Use `process.nextTick()` instead.
@technicalpickles alternatively we could create releases for past versions and put the changes in each release note, would you like me to do that? |
see
semantic-release
to Hubot 🤖 evolution#6for a release to happen, we have to add another commit which can be done using
--allow-empty
.hubot@3
comes with a new feature and 3 breaking changes. The commit can look as follows: