-
Notifications
You must be signed in to change notification settings - Fork 79
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
Add changelog for the next release #487
Conversation
@@ -6,6 +6,38 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/). | |||
This project mirrors major Elm versions. So version 0.18.\* of this project will | |||
be compatible with Elm 0.18.\*. | |||
|
|||
## 0.19.1-beta1.revision5 - 2020-TBA |
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 that according to the semver
module:
0.19.1-beta1.revision5 < 0.19.1-revision5
0.19.1-revision5.beta1 > 0.19.1-revision5
What I’m trying to say is that we need to be careful when choosing the suffix so tools like ncu
/npm-upgrade
don’t think that the beta is a later version than the final revision5
.
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.
Lets not do a beta release. I think the quality is pretty good, I have been using the master with no issues.
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.
Let's just release properly. We can always to a bugfix, its a 0.x version after all.
@@ -6,6 +6,38 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/). | |||
This project mirrors major Elm versions. So version 0.18.\* of this project will | |||
be compatible with Elm 0.18.\*. | |||
|
|||
## 0.19.1-beta1.revision5 - 2020-TBA |
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.
Lets not do a beta release. I think the quality is pretty good, I have been using the master with no issues.
Feel free to change the version and date when doing the release. |
Closes #468
@harrysarson Feel free to close this PR you’d rather write the changelog yourself. I’m sure it can be used as inspiration/a checklist at least! Also feel free to push directly to this branch if you want to tweak something – or do a regular review on GitHub. Whatever you feel like.
Random note:
When releasing, we need to:
version
in package.json and package-lock.json.npm publish --tag beta
.--tag beta
is important, so that we only update ourbeta
tag and notlatest
. Runnpm dist-tag elm-test
to see our current tags: