Add deterministic tenant dependency normalization - #104
Merged
Conversation
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
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.
Tenant Dependency Normalization
Summary
platform dependencies normalizefor canonical tenantuv.lockregenerationupgrade flags
roll back atomically on failure
Validation
uv sync --lockeduv run python -m unittest discover -s tests— 245 passed, 1 skippeduv run ruff format --check .uv run ruff check .uv lock --check --offline --no-config --project docker/runtime-pythonuv buildpre-existing/outside the PR diff, with no finding on added lines
9f0ea308da23fe7ec77e214dc335766c0a72ef889f0ea308da23fe7ec77e214dc335766c0a72ef88Closes #97
Refs cbusillo/launchplane#1935
This PR intentionally does not begin
cbusillo/odoo-tenant-opw#113.