chore(deps): update deno

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
deno_config	workspace.dependencies	minor	0.97.0 → 0.105.0	0.106.0
deno_lockfile	dependencies	minor	0.49.0 → 0.57.0	0.58.0
deno_package_json	dependencies	minor	0.49.0 → 0.57.0	0.58.0
deno_semver (source)	workspace.dependencies	minor	0.9.0 → 0.10.0
jsonc-parser	dependencies	minor	0.32.0 → 0.33.0	0.33.1

---

Release Notes

denoland/deno_semver (deno_semver)

v0.10.1

Compare Source

• fix: clearer error when version is missing minor/patch component (#​54)

v0.10.0

Compare Source

• perf: monch 0.6 (#​52)

dprint/jsonc-parser (jsonc-parser)

v0.33.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• 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 is behind base branch, 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]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: crates/knope-versioning/Cargo.toml

Artifact update for jsonc-parser resolved to version 0.33.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.33.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/