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

Announce: change in versioning scheme #2288

ry opened this issue May 3, 2019 · 2 comments


2 participants
Copy link

commented May 3, 2019

We've been incrementing the patch number in the releases each week, while introducing large changes. (This is actually allowed inside of semver, as it's v0.y.z still.) However, moving forward I would like to start incrementing the minor version each week, starting this week.

So very soon we will release "v0.4.0", and next week "v0.5.0". If there are small fixes made to a release, we'll increment the patch number (an example of this would have been the v0.3.10 release).

I will migrate all the issues tagged with "v0.4" to "v1.0".

The CLI API has changed radically in the last few weeks, so this seems as good a time as any to make this change.

I just want to forewarn people that "v0.4.0" doesn't mean that we've reached a new level of stability. We're still under heavy development and I expect that to continue throughout the summer.

@ry ry changed the title Announce: changing in versioning scheme Announce: change in versioning scheme May 3, 2019

@ry ry referenced this issue May 3, 2019


v0.4.0 #2289


This comment has been minimized.

Copy link

commented May 4, 2019

Is deno_std concerned with this change?


This comment has been minimized.

Copy link
Collaborator Author

commented May 4, 2019

@zekth Not really. It will continued to be tagged and versioned along with Deno. Which btw, I've just pushed the tag for v0.4.0

@ry ry closed this May 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.