Skip to content

Releases: JS-DevTools/npm-publish

v3.1.1

29 Mar 02:05
v3.1.1
19c28f1
Compare
Choose a tag to compare

Bug fixes

  • include registry URL pathname in npm config (#186)

v3.1.0

22 Mar 22:03
v3.1.0
79051c0
Compare
Choose a tag to compare

Features

  • dry-run: always print publish results in dry run (#185), closes #184

Performance Improvements

  • action: decrease bundle size (#166)

v3.0.1

24 Oct 15:44
v3.0.1
4b07b26
Compare
Choose a tag to compare

Bug fixes

  • errors: improve message when version validation fails (#161), closes #160

v3.0.0

18 Oct 20:48
v3.0.0
6fd3bc8
Compare
Choose a tag to compare

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

13 Sep 01:26
v2.2.2
fe72237
Compare
Choose a tag to compare

Bug Fixes

  • use validated package.json version for comparisons (#147), closes #139

v2.2.1

11 Jul 16:30
v2.2.1
5a85faf
Compare
Choose a tag to compare

Bug Fixes

  • action: update semver dep, esbuild and vitest dev deps (#114)
  • npm: do not assume error code is a string (#120), closes #119

v2.2.0

02 Jun 21:21
a25b418
Compare
Choose a tag to compare

Features

  • Allow --ignore-scripts to be disabled in order to support publish lifecycle hooks (#102)

v2.1.0

02 May 14:37
v2.1.0
541aa6b
Compare
Choose a tag to compare

Features

  • Add explicit support for --provenance (#92), closes #88

Bug Fixes

  • Handle missing latest tag during version check (#90), closes #89

v2.0.0

20 Apr 14:58
v2.0.0
0be441d
Compare
Choose a tag to compare

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 of none when no release occurs

    - - if: ${{ steps.publish.outputs.type != 'none' }}
    + - if: ${{ steps.publish.outputs.type }}
        run:  echo "Version changed!"
  • The check-version and greater-version-only options have been removed and replaced with strategy.

    • 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; use npm directly, instead.
  • 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 the token option is now required.

Features

  • tag, access, and registry now fall back to publishConfig in package.json, if specified. (#36)
  • The package argument may now be a directory, and is passed to npm publish as its package_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

21 Jan 14:00
Compare
Choose a tag to compare

Initial release.