v1.9

Merge pull request #69 from thefrontside/mk/fix-dockerfiles

Specify python2 for dockerfiles for v1 actions

v1.7

Validate instead of filter for synchronize-with-npm (#62)

* Modify synchronize-with-npm to validate instead of relying on git diff

* Update README

v1.6

Use deprecate property in package.json as deprecate message (#60)

v1.5

Push git tags when pull request is merged to master (#56)

* Git tag for release action

* Reorder authentication url

* Remove tags flag

v1.4

Add before_all argument for both release and preview actions (#55)

v1.3

Add monorepo support for release action (synchronize-with-npm) (#54)

* Add monorepo support for release action

* Update Dockerfile to be compatible with new action

v1.2

v1.1 → v1.2

What's new in v1.2?

The changes for v1.2 is strictly to enhance the publish-pr-preview action so synchronize-npm-tags and synchronize-with-npm actions can still be called from v1.2 but it will be the same as v1.1 for those two actions.

This pull request describes the changes in v1.2 for the publish-pr-preview action:

• Authenticates for npmjs by default unless user configures otherwise (in their repository).
• Sets unsafe-perm in-line with yarn/npm-install.
• Removed SCOPES argument because user should configure that themselves if they need to fetch dependencies from private organizations.
• Changed the name of NPM_AUTH_TOKEN to NPM_TOKEN
• Updated the README

v1.1

v1 → v1.1

Context

v1 was released because of an error we occurred on effection.js. v1 allowed for the usage of the publish-pr-preview action before we implemented monorepo support which avoids some of the overlooked conflicts/confusion with the .npmrc file placement. Those issues have been addressed in this pull request.

What's new in v1.1?

We're backtracking a little here but here are the key differences:

• Removed (PR #31) npm-publish-branch-preview, post-npm-usage-instructions-comment, and write-npm-snapshot-version because they were refactored (PR #29) into one action: publish-pr-preview.
• Added monorepo support to publish-pr-preview which, aside from the issue mentioned above, maintains the same functionality for single repositories.
• Added better instructional/warning comments for more specific scenarios.