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

Apply latest nlm generator #4

Merged
merged 2 commits into from
Mar 23, 2016
Merged

Apply latest nlm generator #4

merged 2 commits into from
Mar 23, 2016

Conversation

i-tier-bot
Copy link
Collaborator

This PR was created by a machine.

nlm is a tool for automating the release of node packages. There are some notable implications of using nlm:

  • Commits messages are used to determine the semver implications of the changes.
  • The above means that all commits have to follow the angular commit message conventions so nlm can parse them.
  • Releases happen automatically from CI after successful builds of the master branch. There's no manual intervention required.

Additionally some standard dependency versions were enforced:

  • lodash@^4.6.1
  • bluebird@^3.3.3

/cc @InteractionTier/core

@ageitgey
Copy link
Collaborator

LGTM. Will the License name change have to be re-made every time we run the nlm generator?

@jkrems
Copy link
Member

jkrems commented Mar 23, 2016

No, nlm will never touch an existing license file.

@jkrems jkrems merged commit b0a5adb into master Mar 23, 2016
@jkrems jkrems deleted the apply-nlm-generator branch March 23, 2016 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants