Skip to content

ticket-228: refresh stale internal dependencies in uv.lock - #274

Closed
tom-sapletta-com wants to merge 1 commit into
mainfrom
ticket/228-refresh-internal-deps
Closed

tom-sapletta-com wants to merge 1 commit into
mainfrom
ticket/228-refresh-internal-deps

Conversation

@tom-sapletta-com

Copy link
Copy Markdown
Contributor

Internal dependency freshness fails on main and every PR: clickmd 1.1.15, costs 0.2.0, goal 2.2.0 are outdated. uv.lock is re-resolved with the command the checker prints (uv lock --upgrade-package clickmd==1.1.16 --upgrade-package costs==0.2.1 --upgrade-package goal==2.2.1); the stale pfix entry and packages only it required are dropped. Only uv.lock changes. goal dependencies --check on the new lock: fresh=true. Locked recipe: py3.13 1279 passed (the 1 failure is test_release_availability, fixed by #271). See project/ticket-228/README.md.

@tom-sapletta-com

Copy link
Copy Markdown
Contributor Author

Closing this stale PR as superseded. Its implementation is already present on current main (7c593332be1a1b26fce9a0ea6ecbba8bf8d75cbe), introduced by 63bc48b28d57a80b1f89118f0bf32fe151891242. All non-tracking files in this PR are byte-identical to main. Focused current-main verification: 49 tests passed across release availability, CI readiness, foundation helpers and SQLite/retry performance; governance reported PASS. This closure does not assert that this PR passed independent protected review or was merged. Existing OneDev runs fail PLANFILE_DEPENDENCY_PIN_MISMATCH and remain historical failures. Branches and the external ticket-231 dirty worktree are preserved.

@tom-sapletta-com
tom-sapletta-com deleted the ticket/228-refresh-internal-deps branch October 23, 2026 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant