Update publish-package.sh to include LICENSE file. #2970
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
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
@harvesthq/chosen-developers as follow-up to #2966 (which fixed #2945… almost).
Unfortunately, version 1.8.4 did not include the LICENSE in
chosen-package. Although NPM automatically includes LICENSE files in packages, I overlooked our custompublish-package.shscript run on Travis CI builds of this repo, which has a specific list of files to copy to the folder which will be pushed tochosen-packageand then published by NPM.I believe this is… now… the last thing that needs to be done. Whew!