Repository navigation
ci: bump astral-sh/setup-uv from 10.3.2 to 10.3.3 in the all-actions group - #1135
Conversation
Bumps the all-actions group with 1 update: [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv). Updates `astral-sh/setup-uv` from 10.3.2 to 10.3.3 - [Release notes](https://github.com/astral-sh/setup-uv/releases) - [Commits](astral-sh/setup-uv@07a047e...68559e9) --- updated-dependencies: - dependency-name: astral-sh/setup-uv dependency-version: 10.3.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: all-actions ... Signed-off-by: dependabot[bot] <support@github.com>
svcnvidia-nemo-ci
left a comment
There was a problem hiding this comment.
No qualifying findings.
I reviewed all eight changed workflows, compared their setup-uv pins and inputs with the base, and traced the affected build, test, cache, audit, and publication paths. All 17 references consistently use the new SHA; the uv/Python selections, permissions, and failure gates remain unchanged.
Validation was static: I didn't run tests or workflows, and the upstream action implementation isn't mounted for inspection. This comment-only disposition follows the repository's publication policy.
Review generated by codex. This was a full review. Request a full review with /review reset=true.
|
Fern preview: https://nvidia-preview-pr-1135.docs.buildwithfern.com/nemo/datadesigner
|
Bumps the all-actions group with 1 update: astral-sh/setup-uv.
Updates
astral-sh/setup-uvfrom 10.3.2 to 10.3.3Release notes
Sourced from astral-sh/setup-uv's releases.
Commits
68559e9Use Astral mirror for version manifests with GitHub fallback (#1119)0192b69chore: update known checksums for 0.13.6 (#1117)2f29784docs: use JSDoc for compatible release specifier comment (#1113)9c73321fix: allow whitespace in uv requirement specifiers (#1112)80fbe01fix: resolve ~= specifiers with PEP 440 semantics (#1111)36b7b57fix: only report a saved cache when saving succeeded (#1110)56618cadocs: update version references to v10.3.2 (#1104)Most Recent Ignore Conditions Applied to This Pull Request
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