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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

v0.3.1 #17

merged 2 commits into from Mar 1, 2019


None yet
2 participants
Copy link

sharmilajesupaul commented Feb 28, 2019

I haven't published this change yet.

I'm realizing my change doesn't follow our commit tagging convention and I don't have access to modify commits on master, sorry sorry. 馃槗

But this PR adds the new version bump, along with a changelog.

I'm using auto-changelog for this, running npm version patch|minor|major|v0.3.1 will regenerate the changelog for each release.

@sharmilajesupaul sharmilajesupaul requested review from ljharb and madicap Feb 28, 2019


This comment has been minimized.

Copy link

ljharb commented Feb 28, 2019

I鈥檒l take care of it later tonight.

@ljharb ljharb force-pushed the v0.4.0 branch from 314d873 to 55568f3 Mar 1, 2019

@sharmilajesupaul sharmilajesupaul changed the title V0.4.0 V0.3.1 Mar 1, 2019

@ljharb ljharb force-pushed the v0.4.0 branch from 55568f3 to 4a794a2 Mar 1, 2019

@ljharb ljharb changed the title V0.3.1 v0.3.1 Mar 1, 2019


ljharb approved these changes Mar 1, 2019

@sharmilajesupaul sharmilajesupaul merged commit 4a794a2 into master Mar 1, 2019

@ljharb ljharb deleted the v0.4.0 branch Mar 1, 2019

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