ImperialSquid / zotero-zotts

A Zotero plugin adding text to speech (TTS) functionality to various screens
GNU Affero General Public License v3.0
86 stars 1 forks source link

build(deps-dev): bump release-it from 15.10.2 to 16.2.1 #57

Closed dependabot[bot] closed 5 months ago

dependabot[bot] commented 1 year ago

Bumps release-it from 15.10.2 to 16.2.1.

Release notes

Sourced from release-it's releases.

Release 16.2.1

  • Format Markdown (ebe4fbd)
  • Add production mode config for Knip (c1c0f99)
  • Update dependencies (a3d32ae)
  • Fix initial --snapshot latestVersion (f283230)

Release 16.2.0

  • Update dependencies (f5576f1)
  • Add support for snapshots (--snapshot=feat → v0.0.0-feat.0), alpha/undocumented (6d027fd)
  • Add releaseUrl to message context (resolves #1038) (07f373e)
  • Bump actions/checkout from 3 to 4 (#1039) (d931f36)
  • Update version in the readme (#1036) (e2e0c34)

Release 16.1.5

  • Only show url message on Windows (68b91c4)
  • fix: unable to open the browser automatically on Windows system (#1019) (5069c30)

Release 16.1.4

  • Replace mock-fs with memfs + fs-monkey (723db6c)
  • Update dependencies (a3da2bf)

Release 16.1.3

  • Update dependencies (closes #1024) (79430b4)

Release 16.1.2

  • Revert some updates for Node.js 16 compat (a106c83)

Release 16.1.1

  • Update dependencies (closes #1023) (9d6f183)

Release 16.1.0

  • Edit and move new section about getLatestTagFromAllRefs up in docs (a166ab4)
  • Extend test for getLatestTagFromAllRefs to assert default behavior too (930e80a)
  • test: add a test scenario for git.getLatestTagFromAllRefs (fef97c6)
  • feat: add git.getLatestTagFromAllRefs config item to use all refs to determine latest version, not just reachable commits. (8611ef0)
  • docs: update legacy Node comment on readme page (#1021) (5beacf2)

Release 16.0.0

  • Add v16 to changelog (2e09260)
  • Add knip to deps/scripts (00220ce)
  • Update dependencies + add lockfile (breaking support for Node.js v14/npm v6) (97c233e)

Release 15.11.0

  • Fix regression caused by 46fc8fa (1ea14aa)
  • Remove + ignore .DS_Store (0198b89)
  • Fix lint issue (6158d7e)
  • feat: Adding publicPath option for npm publishConfig (#1010) (fef8566)

Release 15.10.5

  • Downgrade @​octokit/request-error (9b97b46)

... (truncated)

Changelog

Sourced from release-it's changelog.

Changelog

This document lists breaking changes for each major release.

See the GitHub Releases page for detailed changelogs: https://github.com/release-it/release-it/releases

v16 (2023-07-05)

  • Removed support for Node.js v14.

v15 (2022-04-30)

  • Removed support for Node.js v10 and v12.
  • Removed support for GitLab v12.4 and lower.
  • Removed anonymous metrics (and the option to disable it).
  • Programmatic usage and plugins only through ES Module syntax (import)

Use release-it v14 in legacy environments.

v14 (2020-09-03)

  • Removed global property from plugins. Use this.config[key] instead.
  • Removed deprecated npm.access option. Set this in package.json instead.

v13 (2020-03-07)

  • Dropped support for Node v8
  • Dropped support for GitLab v11.6 and lower.
  • Deprecated scripts are removed (in favor of hooks).
  • Removed deprecated --non-interactive (-n) argument. Use --ci instead.
  • Removed old %s and [REV_RANGE] syntax in command substitutions. Use ${version} and ${latestTag} instead.

v12 (2019-05-03)

  • The --follow-tags argument for git push has been moved to the default configuration. This is only a breaking change if git.pushArgs was not empty (it was empty by default).

v11

  • The custom conventional-changelog increment (e.g. "increment": "conventional:angular") with additional script configuration is replaced with a plugin. Please see conventional changelog how to use this plugin.
  • The pkgFiles option has been removed. If there's a need to bump other files than what npm version bumps, it should be (part of) a plugin.
  • By default, the latest version was derived from the latest Git tag. From v11, if the repo has a package.json then that version is used instead. The use option has been removed. Also see latest version.
  • scripts.changelog has been moved to git.changelog

... (truncated)

Commits


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)
dependabot[bot] commented 5 months ago

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.