Releases: JS-DevTools/npm-publish
v3.1.1
Bug fixes
- include registry URL pathname in npm config (#186)
v3.1.0
v3.0.1
v3.0.0
The v3 release updates the action's runtime to Node.js v20, but otherwise, there are no public API changes.
BREAKING CHANGES
- The action will now run on Node.js v20 instead of v16
Bug fixes
- action: update runtime to Node.js v20 (#150)
v2.2.2
v2.2.1
v2.2.0
Features
- Allow
--ignore-scripts
to be disabled in order to support publish lifecycle hooks (#102)
v2.1.0
v2.0.0
Welcome to v2 of JS-DevTools/npm-publish! We've been doing some spring cleaning to fix all our (known) bugs and knock out some longstanding feature requests. This release has some breaking changes, so please read carefully!
BREAKING CHANGES
-
The
type
output is now an empty string instead ofnone
when no release occurs- - if: ${{ steps.publish.outputs.type != 'none' }} + - if: ${{ steps.publish.outputs.type }} run: echo "Version changed!"
-
The
check-version
andgreater-version-only
options have been removed and replaced withstrategy
.- Use
strategy: all
(default) to publish all versions that do not yet exist in the registry.with: token: ${{ secrets.NPM_TOKEN }} - check-version: true - greater-version-only: false + strategy: all
- Use
strategy: upgrade
to only publish versions that upgrade the selected tag.with: token: ${{ secrets.NPM_TOKEN }} - check-version: true - greater-version-only: true + strategy: upgrade
check-version: false
has been removed. You don't need this action if you're not checking already published versions; usenpm
directly, instead.
- Use
-
The library and CLI now require Node v16 or later. They may technically work in earlier versions, but they're not tested in CI and you will have to tell your package manager to ignore the
engines
requirement. -
The library and CLI no longer read the user's
~/.npmrc
file, so thetoken
option is now required.
Features
tag
,access
, andregistry
now fall back topublishConfig
inpackage.json
, if specified. (#36)- The
package
argument may now be a directory, and is passed tonpm publish
as itspackage_spec
argument. (#59) - The
package
argument may also be a pre-packed.tgz
archive (#81)
Bug fixes
- The user's
~/.npmrc
file is no longer modified. Instead, a temporary.npmrc
file is used. (#15) npm
is now always called with--ignore-scripts
for security (#47)npm
is now always called in the current working directory (#51)- The action was updated to use the Node v16 runtime. (#61)
- The
@actions/core
dependency was upgraded to fix deprecation warnings. (#67)
v1.0.0
Initial release.