Bump astral-sh/setup-uv from 4 to 6 - #15
Merged
dependabot[bot] merged 1 commit intoAug 14, 2025
Merged
Conversation
dependabot
Bot
added
dependencies
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 4 to 6. - [Release notes](https://github.com/astral-sh/setup-uv/releases) - [Commits](astral-sh/setup-uv@v4...v6) --- updated-dependencies: - dependency-name: astral-sh/setup-uv dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/astral-sh/setup-uv-6
branch
from
August 14, 2025 16:01
f2105f0 to
d28b6be
Compare
Member
|
@dependabot merge |
dependabot
Bot
deleted the
dependabot/github_actions/astral-sh/setup-uv-6
branch
August 14, 2025 16:13
bosd
pushed a commit
that referenced
this pull request
Aug 1, 2026
… + --no-cache The on-disk id-map cache was keyed only by host+port+db. After the target database is rebuilt (or a *different* dump is restored under the same name), the record ids change but the key doesn't, so cached natural-key -> db-id mappings silently point at whatever now owns those ids — wrong-record writes with no warning. Fold the Odoo `database.uuid` (ir.config_parameter) into the cache fingerprint: a rebuild/re-init mints a new uuid (fresh cache), while a pg_restore of the *same* dump preserves it (and the ids), so the cache stays valid — no needless invalidation. The uuid read is best-effort and memoized per connection; a minimal-privilege API user who can't read ir.config_parameter falls back to the old host+port+db key (restore-detection just unavailable for them). Also add a `--no-cache` flag (disables all id-map cache reads/writes for the run) as a universal escape hatch, and dedupe get_cache_dir onto resolve_cache_dir so both share the fingerprint and the switch. Tests cover the uuid fingerprint, the ACL/read-failure fallback, and --no-cache. Full suite: 1435 passed. Docs: a note under the relation pre-resolution section.
bosd
added a commit
that referenced
this pull request
Aug 1, 2026
…o-cache (#225) * fix(#15): invalidate the id-map cache on DB restore via database.uuid + --no-cache The on-disk id-map cache was keyed only by host+port+db. After the target database is rebuilt (or a *different* dump is restored under the same name), the record ids change but the key doesn't, so cached natural-key -> db-id mappings silently point at whatever now owns those ids — wrong-record writes with no warning. Fold the Odoo `database.uuid` (ir.config_parameter) into the cache fingerprint: a rebuild/re-init mints a new uuid (fresh cache), while a pg_restore of the *same* dump preserves it (and the ids), so the cache stays valid — no needless invalidation. The uuid read is best-effort and memoized per connection; a minimal-privilege API user who can't read ir.config_parameter falls back to the old host+port+db key (restore-detection just unavailable for them). Also add a `--no-cache` flag (disables all id-map cache reads/writes for the run) as a universal escape hatch, and dedupe get_cache_dir onto resolve_cache_dir so both share the fingerprint and the switch. Tests cover the uuid fingerprint, the ACL/read-failure fallback, and --no-cache. Full suite: 1435 passed. Docs: a note under the relation pre-resolution section. * test: narrow Optional fingerprint before .endswith (mypy) _connection_fingerprint returns Optional[str]; assert non-None before the suffix checks so full-scope mypy (src tests) passes. --------- Co-authored-by: bosd <5e2fd43-d292-4c90-9d1f-74ff3436329a@anonaddy.me>
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 astral-sh/setup-uv from 4 to 6.
Release notes
Sourced from astral-sh/setup-uv's releases.
... (truncated)
Commits
bd01e18Do not warn when version not in manifest-file (#462)c6a5ebachore: update known versions for 0.7.14 (#459)790df8fRevert "Set expected cache dir drive to C: on windows (#451)" (#460)445689eUse latest version from manifest-file (#458)a02a550Look for version-manifest.json relative to action path (#456)60cc2b4Add input manifest-file (#454)7bbb36fchore: update known versions for 0.7.13 and 0.7.12 (#444)60ecb38Set expected cache dir drive to C: on windows (#451)252c995chore: update known versions for 0.7.11 (#442)477a814chore: update known versions for 0.7.10 (#440)You can trigger a rebase of this PR 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)