Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 9, 2021

This PR contains the following updates:

Package Type Update Change Age Confidence
JS-DevTools/npm-publish action major v1.4.3 -> v3.1.1 age confidence
actions/checkout action major v2.7.0 -> v4.2.2 age confidence
actions/setup-node action major v2.5.2 -> v4.4.0 age confidence
eslint-config-prettier dependencies major ^8.3.0 -> ^10.0.0 age confidence
lint-staged devDependencies major ^15.2.7 -> ^16.0.0 age confidence
node (source) major 20 -> 22 age confidence
typescript (source) dependencies major ^4.5.4 -> ^5.0.0 age confidence

Release Notes

JS-DevTools/npm-publish (JS-DevTools/npm-publish)

v3.1.1

Compare Source

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

v3.1.0

Compare Source

Features
  • dry-run: always print publish results in dry run (#​185), closes #​184
Performance Improvements
  • action: decrease bundle size (#​166)

v3.0.1

Compare Source

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

v3.0.0

Compare Source

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

Compare Source

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

v2.2.1

Compare Source

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

Compare Source

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

v2.1.0

Compare Source

Features
  • Add explicit support for --provenance (#​92), closes #​88
Bug Fixes
  • Handle missing latest tag during version check (#​90), closes #​89

v2.0.0

Compare Source

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)
actions/checkout (actions/checkout)

v4.2.2

Compare Source

v4.2.1

Compare Source

v4.2.0

Compare Source

v4.1.7

Compare Source

v4.1.6

Compare Source

v4.1.5

Compare Source

v4.1.4

Compare Source

v4.1.3

Compare Source

v4.1.2

Compare Source

v4.1.1

Compare Source

v4.1.0

Compare Source

v4.0.0

Compare Source

v3.6.0

Compare Source

v3.5.3

Compare Source

v3.5.2

Compare Source

v3.5.1

Compare Source

v3.5.0

Compare Source

v3.4.0

Compare Source

v3.3.0

Compare Source

v3.2.0

Compare Source

v3.1.0

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

actions/setup-node (actions/setup-node)

v4.4.0

Compare Source

What's Changed
Bug fixes:
Enhancement:
Dependency update:
New Contributors

Full Changelogactions/setup-node@v4...v4.4.0

v4.3.0

Compare Source

What's Changed

Dependency updates

New Contributors

Full Changelog: actions/setup-node@v4...v4.3.0

v4.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/setup-node@v4...v4.2.0

v4.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/setup-node@v4...v4.1.0

v4.0.4

Compare Source

What's Changed

Documentation changes:

New Contributors

Full Changelog: actions/setup-node@v4...v4.0.4

v4.0.3

Compare Source

What's Changed

Bug fixes:
Documentation changes:
Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v4...v4.0.3

v4.0.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4.0.1...v4.0.2

v4.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: actions/setup-node@v4...v4.0.1

v4.0.0

Compare Source

What's Changed

In scope of this release we changed version of node runtime for action from node16 to node20 and updated dependencies in https://github.com/actions/setup-node/pull/866

Besides, release contains such changes as:

New Contributors

Full Changelog: actions/setup-node@v3...v4.0.0

v3.9.1

Compare Source

What's Changed

Full Changelog: actions/setup-node@v3...v3.9.1

v3.9.0

Compare Source

What's Changed

Full Changelog: actions/setup-node@v3...v3.9.0

v3.8.2

Compare Source

What's Changed

Full Changelog: actions/setup-node@v3...v3.8.2

v3.8.1

Compare Source

What's Changed

In scope of this release, the filter was removed within the cache-save step by @​dmitry-shibanov in https://github.com/actions/setup-node/pull/831. It is filtered and checked in the toolkit/cache library.

Full Changelog: actions/setup-node@v3...v3.8.1

v3.8.0

Compare Source

What's Changed
Bug fixes:
Feature implementations:
Documentation changes:
Update dependencies:
New Contributors

Full Changelog: actions/setup-node@v3...v3.8.0

v3.7.0

Compare Source

What's Changed

In scope of this release we added a logic to save an additional cache path for yarn 3 (related pull request and feature request). Moreover, we added functionality to use all the sub directories derived from cache-dependency-path input and add detect all dependencies directories to cache (related pull request and feature request).

Besides, we made such changes as:
New Contributors

Full Changelog: actions/setup-node@v3...v3.7.0

v3.6.0: Add Support for Nightly, Canary and RC builds for Node.js

Compare Source

In scope of this release we added support to download nightly, rc (https://github.com/actions/setup-node/pull/611) and canary (https://github.com/actions/setup-node/pull/619) Node.js distributions.

For nightly versions:
jobs:
  build:
    runs-on: ubuntu-latest
    name: Node sample
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '16-nightly'
      - run: npm ci
      - run: npm test
For canary versions:
jobs:
  build:
    runs-on: ubuntu-latest
    name: Node sample
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '16-v8-canary’
      - run: npm ci
      - run: npm test
For rc versions:
jobs:
  build:
    runs-on: ubuntu-latest
    name: Node sample
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '16.0.0-rc.1’
      - run: npm ci
      - run: npm test

Note: For more examples please refer to documentation.

Besides, we added the following changes as:

v3.5.1: Update @​actions/core and Print Node, Npm, Yarn versions

Compare Source

In scope of this release we updated actions/core to 1.10.0. Moreover, we added logic to print Nodejs, Npm, Yarn versions after installation.

v3.5.0: Add support for engines.node and Volta

Compare Source

In scope of this release we add support for engines.node. The action will be able to grab the version form package.json#engines.node. https://github.com/actions/setup-node/pull/485. Moreover, we added support for Volta

Besides, we updated @​actions/core to 1.9.1 and @​actions/cache to 3.0.4

v3.4.1: Fix pnpm output and node-version output issues

Compare Source

In scope of this release we fixed bugs related to the pnpm 7.5.1 output issue from pnpm store path https://github.com/actions/setup-node/pull/545. Moreover we fixed the issue with falling on node-version output https://github.com/actions/setup-node/pull/540.

v3.4.0: Add support for asdf format and update actions/cache version to 3.0.0

Compare Source

In scope of this release we updated actions/cache package as the new version contains fixes for caching error handling. Moreover, we added support for asdf format as Node.js version file https://github.com/actions/setup-node/pull/373. Besides, we introduced new output node-version and added npm-shrinkwrap.json to dependency file patterns: https://github.com/actions/setup-node/pull/439

v3.3.0: Add support for lts/-n aliases

Compare Source

In scope of this release we added support for lts/-n aliases, improve logic for current, latest and node aliases to handle them from toolcache, update ncc package.

Support of lts/-n aliases
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
  with:
    node-version: lts/-1
- run: npm ci
- run: npm test
Minor improvements

[v3.2.0](https://redirect.github.com/actions/setup-node/release


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-all branch from 991ca4b to 92222df Compare October 26, 2021 01:36
@renovate renovate bot changed the title fix(deps): update dependency eslint to v8 fix(deps): update all (major) Oct 26, 2021
@renovate renovate bot changed the title fix(deps): update all (major) chore(deps): update node.js to v16 Nov 6, 2021
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 042ca64 to 3a9d195 Compare November 13, 2021 20:54
@renovate renovate bot changed the title chore(deps): update node.js to v16 chore(deps): update all (major) Nov 13, 2021
@renovate renovate bot changed the title chore(deps): update all (major) chore(deps): update node.js to v16 Dec 4, 2021
@renovate renovate bot force-pushed the renovate/major-all branch from 3a9d195 to 90c9ae2 Compare December 4, 2021 23:56
@renovate renovate bot force-pushed the renovate/major-all branch from 90c9ae2 to a824059 Compare February 21, 2022 01:20
@renovate renovate bot changed the title chore(deps): update node.js to v16 chore(deps): update all (major) Feb 21, 2022
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from ec13986 to 4cd0993 Compare March 1, 2022 18:50
@renovate renovate bot force-pushed the renovate/major-all branch from 4cd0993 to 5a56b70 Compare April 24, 2022 21:13
@renovate renovate bot force-pushed the renovate/major-all branch from 5a56b70 to 635e9bf Compare May 15, 2022 21:29
@renovate renovate bot force-pushed the renovate/major-all branch from 635e9bf to 650d925 Compare June 18, 2022 16:20
@renovate renovate bot force-pushed the renovate/major-all branch from 650d925 to e5d9bd2 Compare September 25, 2022 16:39
@renovate renovate bot force-pushed the renovate/major-all branch from e5d9bd2 to 3dd8e58 Compare November 20, 2022 20:32
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 98f7aee to 01a2831 Compare March 24, 2023 21:53
@renovate renovate bot force-pushed the renovate/major-all branch from 01a2831 to 28d0c29 Compare April 17, 2023 12:53
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 4dc6643 to 1acf6e4 Compare June 2, 2023 22:24
@renovate renovate bot force-pushed the renovate/major-all branch from 1acf6e4 to 9ba713b Compare June 9, 2023 17:00
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 144bc54 to 74e073b Compare July 11, 2023 16:44
@renovate renovate bot force-pushed the renovate/major-all branch from 74e073b to 776fe20 Compare August 5, 2023 21:37
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 163eaeb to 32c627e Compare August 17, 2023 16:16
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 2d47d19 to a39c609 Compare March 12, 2024 14:32
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 2541b8f to 266bedd Compare March 29, 2024 04:04
@renovate renovate bot force-pushed the renovate/major-all branch from 266bedd to d2df857 Compare April 5, 2024 21:09
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 41db6eb to 4e14a62 Compare April 25, 2024 12:51
@renovate renovate bot force-pushed the renovate/major-all branch from 4e14a62 to c891605 Compare May 8, 2024 20:33
@renovate renovate bot force-pushed the renovate/major-all branch from c891605 to cea8075 Compare May 16, 2024 20:24
@renovate renovate bot force-pushed the renovate/major-all branch from cea8075 to 0ed3cc4 Compare June 12, 2024 19:27
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from ee7e0ec to 15190ec Compare July 13, 2024 23:40
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from c97da7f to 5b56791 Compare September 25, 2024 20:11
@renovate renovate bot force-pushed the renovate/major-all branch from 5b56791 to a7b9b29 Compare October 7, 2024 19:15
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 7294456 to cd7c582 Compare October 29, 2024 15:53
@renovate renovate bot changed the title chore(deps): update all (major) fix(deps): update all (major) Dec 10, 2024
@renovate renovate bot force-pushed the renovate/major-all branch from cd7c582 to da55324 Compare January 13, 2025 18:25
@renovate renovate bot force-pushed the renovate/major-all branch from da55324 to 7c85528 Compare January 27, 2025 06:29
@renovate renovate bot force-pushed the renovate/major-all branch from 7c85528 to 2f27c5e Compare March 17, 2025 04:27
@renovate renovate bot force-pushed the renovate/major-all branch from 2f27c5e to 35e42f0 Compare April 14, 2025 04:45
@renovate renovate bot force-pushed the renovate/major-all branch from 35e42f0 to 1cf68ae Compare May 10, 2025 20:53
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 8d028f4 to 863ee9c Compare July 31, 2025 23:44
@renovate renovate bot force-pushed the renovate/major-all branch from 863ee9c to fea396a Compare August 3, 2025 18:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants