Skip to content
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

Merged
merged 1 commit into from
Jan 28, 2021
Merged

Conversation

lydell
Copy link
Collaborator

@lydell lydell commented Jan 16, 2021

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:

  • Update version in package.json and package-lock.json.
  • Run npm publish --tag beta. --tag beta is important, so that we only update our beta tag and not latest. Run npm dist-tag elm-test to see our current tags:
beta: 0.19.1-revision3
elm0.18.0: 0.18.13-beta4
elm0.19.0: 0.19.0-rev6
elm0.19.1: 0.19.1
latest-0.18.0: 0.18.13-beta4
latest-0.19.0: 0.19.0-rev6
latest-0.19.1: 0.19.1-revision4
latest: 0.19.1-revision4

@@ -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
Copy link
Collaborator Author

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.

Copy link
Collaborator

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.

@lydell lydell marked this pull request as ready for review January 22, 2021 21:49
Copy link
Collaborator

@harrysarson harrysarson left a 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
Copy link
Collaborator

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.

@lydell
Copy link
Collaborator Author

lydell commented Jan 28, 2021

Feel free to change the version and date when doing the release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Release notes for revision 5.
2 participants