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

fix(packages): use conventional-changelog instead of lerna's conventional-commits #9

Merged
merged 2 commits into from
Jan 15, 2018

Conversation

apapko
Copy link
Collaborator

@apapko apapko commented Jan 13, 2018

Fixes #8

PR Checklist

What kind of change does this PR introduce? (add 'x' - [x])

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:
Please check if your PR fulfills the following requirements:

The PR fulfills these requirements:

  • Tests for the changes have been added (for bug fixes / features)

  • Both unit and integration tests pass

  • Docs have been added / updated (for bug fixes / features)

  • The PR title follows conventional commit format:
    commit-type(optional scope): commit description.

    Supported commit types: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test.
    Supported scope: The scope should be the name of the npm package affected (engine, compiler, wire-service, etc.)
    
  • More details on LWC semantic commit can be found here.

Other information:

Please see detailed description in the following issue

@apapko apapko requested a review from trevor-bliss January 13, 2018 01:27
"release:internalcanary": "yarn prepare && lerna publish --canary --skip-git --yes --registry='https://nexus.soma.salesforce.com/nexus/content/repositories/npmjs-internal/'"
"release:internalcanary": "yarn prepare && lerna publish --canary --skip-git --yes --registry='https://nexus.soma.salesforce.com/nexus/content/repositories/npmjs-internal/'",
"changelog": "yarn changelog:generate && yarn changelog:publish",
"changelog:generate": "conventional-changelog -p angular -i CHANGELOG.md -s -r 0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add a devDependency for conventional-changelog-cli since we're using it directly now. Looks like it's getting pulled in by lerna currently.

@apapko apapko changed the title fix(packages): use conventional-changelog instead of learna's conventional-commits fix(packages): use conventional-changelog instead of lerna's conventional-commits Jan 15, 2018
@apapko
Copy link
Collaborator Author

apapko commented Jan 15, 2018

@trevor-bliss added dev-dependency for conventional-changelog-cli, please approve when you get a chance.

@apapko apapko merged commit ef42218 into master Jan 15, 2018
@apapko apapko deleted the apapko/non-lerna-conventional-changelog branch January 15, 2018 19:56
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.

[conventional-changelog] lerna doesn't prompt for release version
2 participants