chore(deps): update dependency knope to v0.21.7

[renovate]

This PR contains the following updates:

Package	Update	Change
knope (source)	minor	0.20.0 → 0.21.7

---

Release Notes

knope-dev/knope (knope)

v0.21.7

Fixes

Require at least one package to be selected to create a change file

Fixes #​1686. Thanks for the report @​t-moe!

v0.21.6

Fixes

• #​1678 cant have a prerelease label with a 'v' in it. (#​1680)

v0.21.5

Features

Add support for updating version numbers in arbitrary text files using regex patterns. You can now specify versioned files with a regex field containing a named capture group called version:

[package]
versioned_files = [
    "Cargo.toml",
    { path = "README.md", regex = 'version:\s+(?<version>\d+\.?\d+\.?\d+)' }
]

This allows Knope to automatically update version numbers in documentation, installation instructions, and other text files that don't have a structured format.

v0.21.4

Features

Add first-class Deno release support to Knope

##​1577 by @​jeckhart

• Detect Deno projects, workspaces, and nested packages so they can be released with Knope
• Reuse the deno_config and deno_lockfile crates to stay current with maintained Deno config and lockfile formats
• Extend release pipeline so Deno projects get version bumps and changelogs consistent with Node.js projects
• Updated Concept docs for Change, Changeset, Package
• Updated Reference docs for Packages and Default Config
• Add tests for deno based projects and workspaces

v0.21.3

Fixes

Fix pre-release versioning when there are no previous stable versions

Previously, if there was not a Git tag containing a previous stable version, Knope would default to "0.0.0".
Because of the special 1.0.0 rules, this also meant there was no way to start a project at a pre-release of 1.0.0
with no prior releases.

Now, if there are no previous stable releases, Knope will use the version in your files instead of calculating a version
based on "0.0.0".

Fixes #​1515, thanks for the report @​hazre!

v0.21.2

Features

• Support workspace.package.version in Cargo.toml

v0.21.1

Features

Add support for customizing release note entries

You can now customize individual entries in release notes to change the formatting or add authors/hashes to entries when available.

v0.21.0

Breaking Changes

Change to default handling of top-level package.json files

When using the default config (no [package] or [packages]), Knope will now treat a top-level package.json file
which contains a workspaces property as the entrypoint into a monorepo and not a single versioned_file package.

Support package-lock.json files

package-lock.json files are now supported
as versioned_files both for single packages and dependencies (in monorepos).

These files will be auto-detected and updated if using the default (no [package] or [packages]) config, so
this is a breaking change for those users.

Features

Add support for dependencies in package.json files

You can now update the dependencies and devDependencies of a package.json like this:

[package]
versioned_files = [
  # Update @​my/package-name in dependencies and devDependencies whenever this package version updates
  { path = "package.json", dependency = "@​my/package-name" }
]

Support for NPM workspaces

Knope now supports NPM-style workspaces when using the default config!

Fixes

Fix multiple versioned files with same path

Previously, if you referenced the same file multiple times in versioned_files, only the first instance would apply.
Now, if you reference the same path multiple times, each instance will be processed sequentially.

Consider a mono-repo where every package should be versioned in lockstep:

[package]
versioned_files = [
  "package.json",
  { path = "package.json", dependency = "aDependency" },  # Before this fix, this was ignored
  "aDependency/package.json"
]

This use-case is now supported!

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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