romcal
romcal copied to clipboard
ci: bump @jsdevtools/npm-publish from 1.4.3 to 3.1.1
Bumps @jsdevtools/npm-publish from 1.4.3 to 3.1.1.
Release notes
Sourced from @jsdevtools/npm-publish
's releases.
v3.1.1
Bug fixes
- include registry URL pathname in npm config (#186)
v3.1.0
Features
Performance Improvements
- action: decrease bundle size (#166)
v3.0.1
Bug fixes
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
Bug Fixes
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
... (truncated)
Commits
19c28f1
chore(release): 3.1.11e4a74d
fix: include registry URL pathname in npm config (#186)79051c0
chore(release): 3.1.0aa4addf
feat(dry-run): always print publish results in dry run (#185)126874f
chore(deps): bump the production group with 2 updates (#180)71fdf93
chore(deps-dev): bump the lint group with 9 updates (#183)e19e66c
chore(deps-dev): bump the development group with 3 updates (#181)9c9fb62
chore(deps-dev): bump the lint group with 10 updates (#178)2e9724f
chore(deps-dev): bump the development group with 5 updates (#176)fe58a59
chore(deps): bump actions/upload-artifact from 3 to 4 (#172)- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by mcous, a new releaser for @jsdevtools/npm-publish
since your current version.
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 <dependency name> 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)
@dependabot rebase
Looks like this PR is already up-to-date with dev! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate
.
@dependabot rebase
@emagnier @tukusejssirs i think this is safe to upgrade, based on how we use it in the publish script not having been touched in the breaking version changes. would one of you that has access to the npm token be able to test it (w/ dry-run), possibly?
I reopened a PR here to manage this upgrade https://github.com/romcal/romcal/pull/545.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version
or @dependabot ignore this minor version
. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore
condition with the desired update_types
to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.