Skip to content

Bump encoding_rs from 0.8.41 to 0.8.42 in the cargo-compatible group across 1 directory - #281

Merged
HackingGate merged 1 commit into
mainfrom
dependabot/cargo/cargo-compatible-7c5d7dbd21
Oct 3, 2026
Merged

HackingGate merged 1 commit into
mainfrom
dependabot/cargo/cargo-compatible-7c5d7dbd21

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the cargo-compatible group with 1 update in the / directory: encoding_rs.

Updates encoding_rs from 0.8.41 to 0.8.42

Commits
  • a155adc Increment version number to 0.8.42
  • 6603aed Attach the multiversion crate to the std feature instead
  • f718b07 docs: multiversion is compiled only with simd-accel
  • 4434afa chore: pull in multiversion only when it is actually used
  • 96138f6 Update main branch in URLs
  • See full diff in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Sep 29, 2026
@coderabbitai

coderabbitai Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: e61c0ce9-b200-4cba-b380-d901450b54ac

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@dependabot dependabot Bot changed the title Bump encoding_rs from 0.8.41 to 0.8.42 in the cargo-compatible group Bump encoding_rs from 0.8.41 to 0.8.42 in the cargo-compatible group across 1 directory Sep 30, 2026
@dependabot
dependabot Bot force-pushed the dependabot/cargo/cargo-compatible-7c5d7dbd21 branch from e51bb1d to a850d5c Compare September 30, 2026 15:41
Bumps the cargo-compatible group with 1 update in the / directory: [encoding_rs](https://github.com/hsivonen/encoding_rs).


Updates `encoding_rs` from 0.8.41 to 0.8.42
- [Commits](hsivonen/encoding_rs@v0.8.41...v0.8.42)

---
updated-dependencies:
- dependency-name: encoding_rs
  dependency-version: 0.8.42
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-compatible
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/cargo/cargo-compatible-7c5d7dbd21 branch from a850d5c to bede0bf Compare October 1, 2026 16:44
@HackingGate HackingGate mentioned this pull request Oct 3, 2026
@HackingGate
HackingGate merged commit d8c43eb into main Oct 3, 2026
12 checks passed
@HackingGate
HackingGate deleted the dependabot/cargo/cargo-compatible-7c5d7dbd21 branch October 3, 2026 09:46
HackingGate added a commit that referenced this pull request Oct 3, 2026
Three engine changes since 1.24.0. A rule whose `files.include` root is not
on disk no longer selects nothing, prints one line on stderr and passes: the
scan exits 2 naming the rule, the root and that the root does not exist. This
holds for every rule, bundled sets included, so a repository that inherits
`default-token-grant` and has no `.github/workflows` is now refused (#294).

The relative-link check removes inline code spans from each line before it
reads links, delimited as CommonMark does: a run of N backticks closes at the
next run of exactly N, and an unmatched run stays literal. A regular
expression in backticks such as `[2-9](\.\d+)` is no longer reported as a
link to a missing file (#295).

A remote counts as GitHub only when its host is github.com, www.github.com or
raw.githubusercontent.com, the one definition private-names and the shim
already used. A GitHub Enterprise remote is no longer asked about on
github.com: unowned-push keeps the allow-list's refusal for it with exit 1,
and the shim's visibility lookup reports could-not-tell. Any other unknown
forge is refused as before (#296).

encoding_rs is 0.8.42 (#281), and CI runs astral-sh/setup-uv 10.2.0 (#280).

A consumer taking the pin to v1.25.0 must have every `files.include` root its
rules name on disk, inherited sets included: a missing root now fails the
scan with exit 2 where it warned, and the fix is to correct the root or remove
it. A consumer pushing to a GitHub Enterprise remote that its allow-list does
not name is now refused where github.com may have answered for it.
HackingGate added a commit that referenced this pull request Oct 3, 2026
Three engine changes since 1.24.0. A rule whose `files.include` root is not
on disk no longer selects nothing, prints one line on stderr and passes: the
scan exits 2 naming the rule, the root and that the root does not exist. This
holds for every rule, bundled sets included, so a repository that inherits
`default-token-grant` and has no `.github/workflows` is now refused (#294).

The relative-link check removes inline code spans from each line before it
reads links, delimited as CommonMark does: a run of N backticks closes at the
next run of exactly N, and an unmatched run stays literal. A regular
expression in backticks such as `[2-9](\.\d+)` is no longer reported as a
link to a missing file (#295).

A remote counts as GitHub only when its host is github.com, www.github.com or
raw.githubusercontent.com, the one definition private-names and the shim
already used. A GitHub Enterprise remote is no longer asked about on
github.com: unowned-push keeps the allow-list's refusal for it with exit 1,
and the shim's visibility lookup reports could-not-tell. Any other unknown
forge is refused as before (#296).

encoding_rs is 0.8.42 (#281), and CI runs astral-sh/setup-uv 10.2.0 (#280).

A consumer taking the pin to v1.25.0 must have every `files.include` root its
rules name on disk, inherited sets included: a missing root now fails the
scan with exit 2 where it warned, and the fix is to correct the root or remove
it. A consumer pushing to a GitHub Enterprise remote that its allow-list does
not name is now refused where github.com may have answered for it.
HackingGate added a commit that referenced this pull request Oct 3, 2026
Three engine changes since 1.24.0. A rule whose `files.include` root is not
on disk no longer selects nothing, prints one line on stderr and passes: the
scan exits 2 naming the rule, the root and that the root does not exist. This
holds for every rule, bundled sets included, so a repository that inherits
`default-token-grant` and has no `.github/workflows` is now refused (#294).

The relative-link check removes inline code spans from each line before it
reads links, delimited as CommonMark does: a run of N backticks closes at the
next run of exactly N, and an unmatched run stays literal. A regular
expression in backticks such as `[2-9](\.\d+)` is no longer reported as a
link to a missing file (#295).

A remote counts as GitHub only when its host is github.com, www.github.com or
raw.githubusercontent.com, the one definition private-names and the shim
already used. A GitHub Enterprise remote is no longer asked about on
github.com: unowned-push keeps the allow-list's refusal for it with exit 1,
and the shim's visibility lookup reports could-not-tell. Any other unknown
forge is refused as before. A remote URL's host now ends at the first `/`, `?`
or `#`, and userinfo is stripped up to the last `@`, so
`https://evil.com#@github.com/acme/widget.git` is read as evil.com, which is
where git pushes, and unowned-push no longer accepts it on the strength of
github.com ownership. Two spellings uphold cannot read the way git does now
name no host and no repository, so unowned-push refuses them as an unreadable
destination: a `%` anywhere in a `scheme://` URL's authority and a `[` in a
scp-like host. A `file://` URL names no host, so it is never asked about on a
forge, and its repository is read from the path like a plain local path, so
the allow-list judges it by its path (#296).

encoding_rs is 0.8.42 (#281), and CI runs astral-sh/setup-uv 10.2.0 (#280).

A consumer taking the pin to v1.25.0 must have every `files.include` root its
rules name on disk, inherited sets included: a missing root now fails the scan
with exit 2 where it warned, and the fix is to correct the root or remove it.
A consumer pushing to a GitHub Enterprise remote that its allow-list does not
name is now refused where github.com may have answered for it. An ssh Host
alias such as `git@github-work:me/repo`, or `ssh.github.com:443`, is no longer
counted as GitHub, so a push through one to a destination the allow-list does
not name is refused; name the destination in the allow-list, or use a
github.com URL. A push through a remote URL carrying a percent-encoded
credential is refused whatever the allow-list names; drop the encoded
credential from the URL.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant