Apply latest nlm generator #79
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jkrems
approved these changes
Jan 2, 2018
dbushong
reviewed
Jan 2, 2018
.travis.yml
Outdated
| - npm install -g npm@latest-2 | ||
| before_deploy: | ||
| - git config user.email "opensource@groupon.com" | ||
| - git config user.name "Groupon" |
There was a problem hiding this comment.
don't need these 5 lines anymore
markowsiak
force-pushed
the
apply-nlm-generator
branch
from
dbaa76f
to
9ea499a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
bluebird@^3.3.3
lodash@^4.6.1