Repository navigation
ci: remove flatt package proxy integration - #72
Merged
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.
Resolve the core and Docling bridge from official PyPI instead of the Takumi Guard proxy. Remove five proxy Action steps and the Dependabot registry override. Before the tooling transition, all 65 core and 42 bridge package versions and artifact hash sets matched the old locks; after it, all non-lint dependencies remain unchanged and the seven-day cooldown is retained.
Use pinned Ruff and ty lint groups to follow the required Python toolchain. Preserve existing negative tests for frozen attributes and invalid profiles with explicit, test-only type-checker comments; type the token fixture precisely. No production Python code or runtime dependencies change. Add CI validation of the bridge and both package builds while preserving all existing required job names, draft gates, OIDC and tag release protections. Accepted ADRs remain unchanged.
Validation: core just check (349 tests, zero lint/type findings, three Semgrep rule tests, zero source findings, generated docs unchanged); bridge gate (30 tests); both sdists/wheels; extras-free Python 3.11 core installation; four draft-policy tests; actionlint. No release or publication was invoked.