Skip to content

Use standard-version to automate release tasks #85

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.

Sign up for GitHub

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

Jump to bottom
Closed
abmusse opened this issue Oct 14, 2019 · 0 comments · Fixed by #86
Closed

Use standard-version to automate release tasks #85

abmusse opened this issue Oct 14, 2019 · 0 comments · Fixed by #86
Labels
enhancement New feature or request

Comments

@abmusse
Copy link
Member

abmusse commented Oct 14, 2019

standard-version does the following:

  1. bumps the version in metadata files (package.json, composer.json, etc).
  2. uses conventional-changelog to update CHANGELOG.md
  3. commits package.json (et al.) and CHANGELOG.md
  4. tags a new release

Our commits would need to follow the Conventional Commits Spec.

Following these conventions would allow us to auto generate CHANGELOG.md based on our commits.
@abmusse abmusse added the enhancement New feature or request label Oct 14, 2019
@abmusse abmusse mentioned this issue Oct 14, 2019
Merged
kadler pushed a commit that referenced this issue Jan 13, 2020
@abmusse @kadler
feat: use standard-version #85
45f66a7 
standard-version does the following:

1. bumps the version in metadata files (package.json, composer.json, etc).
2. uses conventional-changelog to update CHANGELOG.md
3. commits package.json (et al.) and CHANGELOG.md
4. tags a new release

Added `release` script in package.json: `npm run release`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add CHANGELOG
1 participant
@abmusse