Bump astral-sh/setup-uv from 10.1.0 to 10.2.0 in the actions group - #280
Merged
Merged
Conversation
Bumps the actions group with 1 update: [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv). Updates `astral-sh/setup-uv` from 10.1.0 to 10.2.0 - [Release notes](https://github.com/astral-sh/setup-uv/releases) - [Commits](astral-sh/setup-uv@v10.1.0...v10.2.0) --- updated-dependencies: - dependency-name: astral-sh/setup-uv dependency-version: 10.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
Merged
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the actions group with 1 update: astral-sh/setup-uv.
Updates
astral-sh/setup-uvfrom 10.1.0 to 10.2.0Release notes
Sourced from astral-sh/setup-uv's releases.
Commits
c18668achore(deps): roll up Dependabot updates (#1059)ffe1476chore: update known checksums for 0.12.17 (#1058)f5548c5chore: update known checksums for 0.12.16 (#1057)a761a4eDisable automatic cache saves for merge queues (#1056)3377a30chore: update known checksums for 0.12.15 (#1054)dfb5f38chore: update known checksums for 0.12.14 (#1053)45c121fchore: update known checksums for 0.12.13 (#1045)8073452docs: update version references to v10.1.0 (#1044)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions