luc-ass / homebridge-evohome

Homebridge plugin for Honeywell Evohome
29 stars 16 forks source link

Bump JS-DevTools/npm-publish from 2 to 3 #159

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 8 months ago

Bumps JS-DevTools/npm-publish from 2 to 3.

Release notes

Sourced from JS-DevTools/npm-publish's releases.

v3.0.0

The v3 release updates the action's runtime to Node.js v20, but otherwise, there are 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

Bug Fixes

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

v2.2.1

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

Features

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

v2.1.0

Features

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

Bug Fixes

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

Sourced from JS-DevTools/npm-publish's changelog.

v1.4.0 (2020-10-02)

  • Added support NPM's --tag argument, which allows packages to be published to a named tag that can then be installed using npm install <package-name>@<tag>

  • Added support for NPM's --access argument, which controls whether scoped packages are publicly accessible, or restricted to members of your NPM organization

Full Changelog

v1.3.0 (2020-10-01)

  • NPM-Publish can now successfully publish a brand-new package to NPM. Previously it failed because it couldn't determine the previous package version. ([PR #12](JS-DevTools/npm-publish#12) from @​ZitRos)

Full Changelog

v1.2.0 (2020-07-23)

  • Added support for running NPM in "dry run" mode, which doesn't actually publish, but reports details of what would have been published.

Full Changelog

v1.1.0 (2020-03-29)

  • FIX: The configured NPM registry and token are now used all NPM commands, not just for publishing. This ensures that npm-publish works with private packages and custom registries

Full Changelog

v1.0.0 (2020-01-21)

Initial release 🎉

Commits
  • 6fd3bc8 fix!(action): update runtime to Node.js v20 (#150)
  • 7f426c9 chore(deps): bump the lint group with 7 updates (#159)
  • 806badd chore(deps-dev): bump the development group with 4 updates (#156)
  • See full diff in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)