Files
oxc/deny.toml
T
renovate 14d803a578 chore(deps): update rust crates (#16575)
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [hashbrown](https://redirect.github.com/rust-lang/hashbrown) | workspace.dependencies | patch | `0.16.0` -> `0.16.1` |
| [indexmap](https://redirect.github.com/indexmap-rs/indexmap) | workspace.dependencies | patch | `2.12.0` -> `2.12.1` |
| [insta](https://insta.rs/) ([source](https://redirect.github.com/mitsuhiko/insta)) | workspace.dependencies | minor | `1.43.2` -> `1.44.3` |
| [log](https://redirect.github.com/rust-lang/log) | workspace.dependencies | patch | `0.4.28` -> `0.4.29` |
| [syn](https://redirect.github.com/dtolnay/syn) | workspace.dependencies | patch | `2.0.110` -> `2.0.111` |
| [tower-lsp-server](https://redirect.github.com/tower-lsp-community/tower-lsp-server) | workspace.dependencies | minor | `0.22.1` -> `0.23.0` |
| [tracing-subscriber](https://tokio.rs) ([source](https://redirect.github.com/tokio-rs/tracing)) | workspace.dependencies | patch | `0.3.20` -> `0.3.22` |

---

### Release Notes

<details>
<summary>rust-lang/hashbrown (hashbrown)</summary>

### [`v0.16.1`](https://redirect.github.com/rust-lang/hashbrown/blob/HEAD/CHANGELOG.md#0161---2025-11-20)

[Compare Source](https://redirect.github.com/rust-lang/hashbrown/compare/v0.16.0...v0.16.1)

##### Added

- Added `HashTable` methods related to the raw bucket index ([#&#8203;657](https://redirect.github.com/rust-lang/hashbrown/issues/657))
- Added `VacantEntryRef::insert_with_key` ([#&#8203;579](https://redirect.github.com/rust-lang/hashbrown/issues/579))

##### Changed

- Removed specialization for `Copy` types ([#&#8203;662](https://redirect.github.com/rust-lang/hashbrown/issues/662))
- The `get_many_mut` family of methods have been renamed to `get_disjoint_mut`
  to match the standard library. The old names are still present for now, but
  deprecated. ([#&#8203;648](https://redirect.github.com/rust-lang/hashbrown/issues/648))
- Recognize and use over-sized allocations when using custom allocators. ([#&#8203;523](https://redirect.github.com/rust-lang/hashbrown/issues/523))
- Depend on `serde_core` instead of `serde`. ([#&#8203;649](https://redirect.github.com/rust-lang/hashbrown/issues/649))
- Optimized `collect` on rayon parallel iterators. ([#&#8203;652](https://redirect.github.com/rust-lang/hashbrown/issues/652))

</details>

<details>
<summary>indexmap-rs/indexmap (indexmap)</summary>

### [`v2.12.1`](https://redirect.github.com/indexmap-rs/indexmap/blob/HEAD/RELEASES.md#2121-2025-11-20)

[Compare Source](https://redirect.github.com/indexmap-rs/indexmap/compare/2.12.0...2.12.1)

- Simplified a lot of internals using `hashbrown`'s new bucket API.

</details>

<details>
<summary>mitsuhiko/insta (insta)</summary>

### [`v1.44.3`](https://redirect.github.com/mitsuhiko/insta/blob/HEAD/CHANGELOG.md#1443)

[Compare Source](https://redirect.github.com/mitsuhiko/insta/compare/1.44.2...1.44.3)

- Fix a regression in 1.44.2 where merge conflict detection was too aggressive, incorrectly flagging snapshot content containing `======` or similar patterns as conflicts. [#&#8203;832](https://redirect.github.com/mitsuhiko/insta/issues/832)
- Fix a regression in 1.42.2 where inline snapshot updates would corrupt the file when code preceded the macro (e.g., `let output = assert_snapshot!(...)`). [#&#8203;833](https://redirect.github.com/mitsuhiko/insta/issues/833)

### [`v1.44.2`](https://redirect.github.com/mitsuhiko/insta/blob/HEAD/CHANGELOG.md#1442)

[Compare Source](https://redirect.github.com/mitsuhiko/insta/compare/1.44.1...1.44.2)

- Fix a rare backward compatibility issue where inline snapshots using an uncommon legacy format (single-line content stored in multiline raw strings) could fail to match after 1.44.0. [#&#8203;830](https://redirect.github.com/mitsuhiko/insta/issues/830)
- Handle merge conflicts in snapshot files gracefully. When a snapshot file contains git merge conflict markers, insta now detects them and treats the snapshot as missing, allowing tests to continue and create a new pending snapshot for review. [#&#8203;829](https://redirect.github.com/mitsuhiko/insta/issues/829)
- Skip nextest\_doctest tests when cargo-nextest is not installed. [#&#8203;826](https://redirect.github.com/mitsuhiko/insta/issues/826)
- Fix functional tests failing under nextest due to inherited `NEXTEST_RUN_ID` environment variable. [#&#8203;824](https://redirect.github.com/mitsuhiko/insta/issues/824)

### [`v1.44.1`](https://redirect.github.com/mitsuhiko/insta/blob/HEAD/CHANGELOG.md#1441)

[Compare Source](https://redirect.github.com/mitsuhiko/insta/compare/1.44.0...1.44.1)

- Add `--dnd` alias for `--disable-nextest-doctest` flag to make it easier to silence the deprecation warning. [#&#8203;822](https://redirect.github.com/mitsuhiko/insta/issues/822)
- Update cargo-dist to 0.30.2 and fix Windows runner to use windows-2022. [#&#8203;821](https://redirect.github.com/mitsuhiko/insta/issues/821)

### [`v1.44.0`](https://redirect.github.com/mitsuhiko/insta/blob/HEAD/CHANGELOG.md#1440)

[Compare Source](https://redirect.github.com/mitsuhiko/insta/compare/1.43.2...1.44.0)

- Added non-interactive snapshot review and reject modes for use in non-TTY environments
  (LLMs, CI pipelines, scripts). `cargo insta review --snapshot <path>` and
  `cargo insta reject --snapshot <path>` now work without a terminal. Enhanced
  `pending-snapshots` output with usage instructions and workspace-relative paths. [#&#8203;815](https://redirect.github.com/mitsuhiko/insta/issues/815)
- Add `--disable-nextest-doctest` flag to `cargo insta test` to disable running doctests with
  nextest. Shows a deprecation warning when nextest is used with doctests without this flag, to prepare `cargo insta` to no longer run
  a separate doctest process when using nextest in the future. [#&#8203;803](https://redirect.github.com/mitsuhiko/insta/issues/803)
- Add ergonomic `--test-runner-fallback` / `--no-test-runner-fallback` flags to `cargo insta test`. [#&#8203;811](https://redirect.github.com/mitsuhiko/insta/issues/811)
- Apply redactions to snapshot metadata. [#&#8203;813](https://redirect.github.com/mitsuhiko/insta/issues/813)
- Remove confusing 'previously unseen snapshot' message. [#&#8203;812](https://redirect.github.com/mitsuhiko/insta/issues/812)
- Speed up JSON float rendering. [#&#8203;806](https://redirect.github.com/mitsuhiko/insta/issues/806) ([@&#8203;nyurik](https://redirect.github.com/nyurik))
- Allow globset version up to 0.4.16. [#&#8203;810](https://redirect.github.com/mitsuhiko/insta/issues/810) ([@&#8203;g0hl1n](https://redirect.github.com/g0hl1n))
- Improve documentation. [#&#8203;814](https://redirect.github.com/mitsuhiko/insta/issues/814) ([@&#8203;tshepang](https://redirect.github.com/tshepang))
- We no longer trim starting newlines during assertions, which allows asserting
  the number of leading newlines match. Existing assertions with different
  leading newlines will pass and print a warning suggesting running with
  `--force-update-snapshots`.  They may fail in the future.  (Note that we still
  currently allow differing *trailing* newlines, though may adjust this in the
  future).  [#&#8203;563](https://redirect.github.com/mitsuhiko/insta/issues/563)

</details>

<details>
<summary>rust-lang/log (log)</summary>

### [`v0.4.29`](https://redirect.github.com/rust-lang/log/blob/HEAD/CHANGELOG.md#0429---2025-12-02)

[Compare Source](https://redirect.github.com/rust-lang/log/compare/0.4.28...0.4.29)

</details>

<details>
<summary>dtolnay/syn (syn)</summary>

### [`v2.0.111`](https://redirect.github.com/dtolnay/syn/releases/tag/2.0.111)

[Compare Source](https://redirect.github.com/dtolnay/syn/compare/2.0.110...2.0.111)

- Allow first argument of `braced!`, `bracketed!`, `parenthesized!` to be an otherwise unused variable ([#&#8203;1946](https://redirect.github.com/dtolnay/syn/issues/1946))

</details>

<details>
<summary>tower-lsp-community/tower-lsp-server (tower-lsp-server)</summary>

### [`v0.23.0`](https://redirect.github.com/tower-lsp-community/tower-lsp-server/blob/HEAD/CHANGELOG.md#0230---2025-12-07)

[Compare Source](https://redirect.github.com/tower-lsp-community/tower-lsp-server/compare/v0.22.1...v0.23.0)

##### Added

- add Amber LSP to README Projects section ([#&#8203;66](https://redirect.github.com/tower-lsp-community/tower-lsp-server/issues/66))
- support `window/workDoneProgress/create` requests

##### Changed

- Change the LSP specification types library from `gluon-lang/lsp-types` (which was unmaintained) to `tower-lsp-community/ls-types` (our fork).

  The initial release manually fixes typos that are blocking for some projects.

  In the long term, ls-types will take the approach of codegen based on the types model provided by the LSP specification. This should remove any kind of typos or documentation desync. See [tower-lsp-community/ls-types#22 (comment)](https://redirect.github.com/tower-lsp-community/ls-types/issues/22#issuecomment-3483189800).

##### Fixed

- use `WorkspaceSymbolResponse` in `symbol()` return value

</details>

<details>
<summary>tokio-rs/tracing (tracing-subscriber)</summary>

### [`v0.3.22`](https://redirect.github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.22): tracing-subscriber 0.3.22

[Compare Source](https://redirect.github.com/tokio-rs/tracing/compare/tracing-subscriber-0.3.21...tracing-subscriber-0.3.22)

##### Important

The previous release [0.3.21] was yanked as it depended explicitly on
[tracing-0.1.42], which was yanked due to a breaking change (see [#&#8203;3424] for
details). This release contains all the changes from the previous release, plus
an update to the newer version of `tracing`.

##### Changed

- `tracing`: updated to 0.1.43 ([#&#8203;3427])

[#&#8203;3424]: https://redirect.github.com/tokio-rs/tracing/pull/3424

[#&#8203;3427]: https://redirect.github.com/tokio-rs/tracing/pull/3427

[0.3.21]: https://redirect.github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.21

[tracing-0.1.42]: https://redirect.github.com/tokio-rs/tracing/releases/tag/tracing-0.1.42

### [`v0.3.21`](https://redirect.github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.21): tracing-subscriber 0.3.21

[Compare Source](https://redirect.github.com/tokio-rs/tracing/compare/tracing-subscriber-0.3.20...tracing-subscriber-0.3.21)

##### Fixed

- Change registry exit to decrement local span ref only ([#&#8203;3331])
- Make Layered propagate `on_register_dispatch` ([#&#8203;3379])

##### Changed

- `tracing`: updated to 0.1.42 ([#&#8203;3418])

##### Performance

- Remove `clone_span` on enter ([#&#8203;3289])

##### Documented

- Fix a few small things in the format module ([#&#8203;3339])
- Fix extra closing brace in layer docs ([#&#8203;3350])
- Fix link in `FmtSpan` docs ([#&#8203;3411])

[#&#8203;3289]: https://redirect.github.com/tokio-rs/tracing/pull/#&#8203;3289

[#&#8203;3331]: https://redirect.github.com/tokio-rs/tracing/pull/#&#8203;3331

[#&#8203;3339]: https://redirect.github.com/tokio-rs/tracing/pull/#&#8203;3339

[#&#8203;3350]: https://redirect.github.com/tokio-rs/tracing/pull/#&#8203;3350

[#&#8203;3379]: https://redirect.github.com/tokio-rs/tracing/pull/#&#8203;3379

[#&#8203;3411]: https://redirect.github.com/tokio-rs/tracing/pull/#&#8203;3411

[#&#8203;3418]: https://redirect.github.com/tokio-rs/tracing/pull/#&#8203;3418

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 10am on monday" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **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](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/oxc-project/oxc).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi4zMi4yIiwidXBkYXRlZEluVmVyIjoiNDIuMzIuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
2025-12-09 03:06:52 +00:00

255 lines
11 KiB
TOML

# This template contains all of the possible sections and their default values
# Note that all fields that take a lint level have these possible values:
# * deny - An error will be produced and the check will fail
# * warn - A warning will be produced, but the check will not fail
# * allow - No warning or error will be produced, though in some cases a note
# will be
# The values provided in this template are the default values that will be used
# when any section or field is not specified in your own configuration
# This section is considered when running `cargo deny check advisories`
# More documentation for the advisories section can be found here:
# https://embarkstudios.github.io/cargo-deny/checks/advisories/cfg.html
[advisories]
# The path where the advisory database is cloned/fetched into
db-path = "~/.cargo/advisory-db"
# The url(s) of the advisory databases to use
db-urls = ["https://github.com/rustsec/advisory-db"]
# The lint level for crates that have been yanked from their source registry
yanked = "warn"
# A list of advisory IDs to ignore. Note that ignored advisories will still
# output a note when they are encountered.
ignore = [
# "RUSTSEC-0000-0000",
]
# Threshold for security vulnerabilities, any vulnerability with a CVSS score
# lower than the range specified will be ignored. Note that ignored advisories
# will still output a note when they are encountered.
# * None - CVSS Score 0.0
# * Low - CVSS Score 0.1 - 3.9
# * Medium - CVSS Score 4.0 - 6.9
# * High - CVSS Score 7.0 - 8.9
# * Critical - CVSS Score 9.0 - 10.0
# severity-threshold =
# If this is true, then cargo deny will use the git executable to fetch advisory database.
# If this is false, then it uses a built-in git library.
# Setting this to true can be helpful if you have special authentication requirements that cargo-deny does not support.
# See Git Authentication for more information about setting up git authentication.
# git-fetch-with-cli = true
# This section is considered when running `cargo deny check licenses`
# More documentation for the licenses section can be found here:
# https://embarkstudios.github.io/cargo-deny/checks/licenses/cfg.html
[licenses]
# List of explicitly allowed licenses
# See https://spdx.org/licenses/ for list of possible licenses
# [possible values: any SPDX 3.11 short identifier (+ optional exception)].
allow = [
"Apache-2.0",
"BSD-3-Clause",
"ISC",
"MIT",
"MIT-0",
"MPL-2.0",
"OpenSSL",
"Unicode-DFS-2016",
"Unicode-3.0",
"CDLA-Permissive-2.0",
"BSL-1.0",
]
# The confidence threshold for detecting a license from license text.
# The higher the value, the more closely the license text must be to the
# canonical license text of a valid SPDX license file.
# [possible values: any between 0.0 and 1.0].
confidence-threshold = 0.8
# Allow 1 or more licenses on a per-crate basis, so that particular licenses
# aren't accepted for every possible crate as with the normal allow list
exceptions = [
# Each entry is the crate and version constraint, and its specific allow
# list
{ allow = ["Zlib"], name = "foldhash", version = "*" },
]
# Some crates don't have (easily) machine readable licensing information,
# adding a clarification entry for it allows you to manually specify the
# licensing information
[[licenses.clarify]]
# The name of the crate the clarification applies to
name = "ring"
# The optional version constraint for the crate
version = "*"
# The SPDX expression for the license requirements of the crate
expression = "MIT AND ISC AND OpenSSL"
# One or more files in the crate's source used as the "source of truth" for
# the license expression. If the contents match, the clarification will be used
# when running the license check, otherwise the clarification will be ignored
# and the crate will be checked normally, which may produce warnings or errors
# depending on the rest of your configuration
license-files = [
# Each entry is a crate relative path, and the (opaque) hash of its contents
{ path = "LICENSE", hash = 0xbd0eed23 },
]
[licenses.private]
# If true, ignores workspace crates that aren't published, or are only
# published to private registries.
# To see how to mark a crate as unpublished (to the official registry),
# visit https://doc.rust-lang.org/cargo/reference/manifest.html#the-publish-field.
ignore = false
# One or more private registries that you might publish crates to, if a crate
# is only published to private registries, and ignore is true, the crate will
# not have its license(s) checked
registries = [
# "https://sekretz.com/registry
]
# This section is considered when running `cargo deny check bans`.
# More documentation about the 'bans' section can be found here:
# https://embarkstudios.github.io/cargo-deny/checks/bans/cfg.html
[bans]
# Lint level for when multiple versions of the same crate are detected
multiple-versions = "warn"
# Lint level for when a crate version requirement is `*`
wildcards = "allow"
# The graph highlighting used when creating dotgraphs for crates
# with multiple versions
# * lowest-version - The path to the lowest versioned duplicate is highlighted
# * simplest-path - The path to the version with the fewest edges is highlighted
# * all - Both lowest-version and simplest-path are used
highlight = "all"
# The default lint level for `default` features for crates that are members of
# the workspace that is being checked. This can be overridden by allowing/denying
# `default` on a crate-by-crate basis if desired.
workspace-default-features = "allow"
# The default lint level for `default` features for external crates that are not
# members of the workspace. This can be overridden by allowing/denying `default`
# on a crate-by-crate basis if desired.
external-default-features = "allow"
# List of crates that are allowed. Use with care!
allow = [
# { name = "ansi_term", version = "=0.11.0" },
]
# List of crates to deny
deny = [
# Each entry the name of a crate and a version range. If version is
# not specified, all versions will be matched.
# { name = "ansi_term", version = "=0.11.0" },
#
# Wrapper crates can optionally be specified to allow the crate when it
# is a direct dependency of the otherwise banned crate
# { name = "ansi_term", version = "=0.11.0", wrappers = [] },
]
# List of features to allow/deny
# Each entry the name of a crate and a version range. If version is
# not specified, all versions will be matched.
# [[bans.features]]
# name = "reqwest"
# Features to not allow
# deny = ["json"]
# Features to allow
# allow = [
# "rustls",
# "__rustls",
# "__tls",
# "hyper-rustls",
# "rustls",
# "rustls-pemfile",
# "rustls-tls-webpki-roots",
# "tokio-rustls",
# "webpki-roots",
# ]
# If true, the allowed features must exactly match the enabled feature set. If
# this is set there is no point setting `deny`
# exact = true
# Certain crates/versions that will be skipped when doing duplicate detection.
skip = [
# { name = "ansi_term", version = "=0.11.0" },
]
# Similarly to `skip` allows you to skip certain crates during duplicate
# detection. Unlike skip, it also includes the entire tree of transitive
# dependencies starting at the specified crate, up to a certain depth, which is
# by default infinite.
skip-tree = [
# { name = "ansi_term", version = "=0.11.0", depth = 20 },
]
# This section is considered when running `cargo deny check sources`.
# More documentation about the 'sources' section can be found here:
# https://embarkstudios.github.io/cargo-deny/checks/sources/cfg.html
[sources]
# Lint level for what to happen when a crate from a crate registry that is not
# in the allow list is encountered
unknown-registry = "warn"
# Lint level for what to happen when a crate from a git repository that is not
# in the allow list is encountered
unknown-git = "warn"
# List of URLs for allowed crate registries. Defaults to the crates.io index
# if not specified. If it is specified but empty, no registries are allowed.
allow-registry = ["https://github.com/rust-lang/crates.io-index"]
# List of URLs for allowed Git repositories
allow-git = []
[sources.allow-org]
# 1 or more github.com organizations to allow git sources for
# github = [""]
# 1 or more gitlab.com organizations to allow git sources for
# gitlab = [""]
# 1 or more bitbucket.org organizations to allow git sources for
# bitbucket = [""]
[graph]
# If 1 or more target triples (and optionally, target_features) are specified,
# only the specified targets will be checked when running `cargo deny check`.
# This means, if a particular package is only ever used as a target specific
# dependency, such as, for example, the `nix` crate only being used via the
# `target_family = "unix"` configuration, that only having windows targets in
# this list would mean the nix crate, as well as any of its exclusive
# dependencies not shared by any other crates, would be ignored, as the target
# list here is effectively saying which targets you are building for.
targets = [
# The triple can be any string, but only the target triples built in to
# rustc (as of 1.40) can be checked against actual config expressions
# { triple = "x86_64-unknown-linux-musl" },
# You can also specify which target_features you promise are enabled for a
# particular target. target_features are currently not validated against
# the actual valid features supported by the target architecture.
# { triple = "wasm32-unknown-unknown", features = ["atomics"] },
]
# When creating the dependency graph used as the source of truth when checks are
# executed, this field can be used to prune crates from the graph, removing them
# from the view of cargo-deny. This is an extremely heavy hammer, as if a crate
# is pruned from the graph, all of its dependencies will also be pruned unless
# they are connected to another crate in the graph that hasn't been pruned,
# so it should be used with care. The identifiers are [Package ID Specifications]
# (https://doc.rust-lang.org/cargo/reference/pkgid-spec.html)
# exclude = []
# If true, metadata will be collected with `--all-features`. Note that this can't
# be toggled off if true, if you want to conditionally enable `--all-features` it
# is recommended to pass `--all-features` on the cmd line instead
all-features = false
# If true, metadata will be collected with `--no-default-features`. The same
# caveat with `all-features` applies
no-default-features = false
# If set, these feature will be enabled when collecting metadata. If `--features`
# is specified on the cmd line they will take precedence over this option.
# features = []
[output]
# When outputting inclusion graphs in diagnostics that include features, this
# option can be used to specify the depth at which feature edges will be added.
# This option is included since the graphs can be quite large and the addition
# of features from the crate(s) to all of the graph roots can be far too verbose.
# This option can be overridden via `--feature-depth` on the cmd line
feature-depth = 1