marvin8/sub2pod
Watch
1
0
Fork
You've already forked sub2pod
 0
Code Issues Pull requests Releases 7 Activity Actions

Finish forge.marvin8.zone migration (stage 2) and bump dependencies #25

Manually merged
marvin8 merged 1 commit from chore/stage2-migration into main 2026-08-19 00:29:34 +00:00
Conversation 3 Commits 1 Files changed 5 +327 -327
agent-pi commented 2026-08-18 23:26:45 +00:00
Collaborator
Copy link

Stage-2 migration cleanup for sub2pod:

  • Point the zaojun pre-commit hook at forge.marvin8.zone (zaojun is fully migrated).
  • Update AGENTS.md release-process wording from Codeberg to forge.marvin8.zone.
  • Bump dependencies (zaojun-driven): cyclopts, bump-my-version, complexipy, prek, pysentry-rs, ruff, ty, uv.
  • Align pre-commit revs (ruff, ty, uv, complexipy) with the bumped pyproject versions.
  • Regenerate uv.lock and pylock.toml.

CI runner references were already on zhuiri/suanni; no container/registry publishing applies (no Containerfile).

Stage-2 migration cleanup for sub2pod: - Point the zaojun pre-commit hook at forge.marvin8.zone (zaojun is fully migrated). - Update AGENTS.md release-process wording from Codeberg to forge.marvin8.zone. - Bump dependencies (zaojun-driven): cyclopts, bump-my-version, complexipy, prek, pysentry-rs, ruff, ty, uv. - Align pre-commit revs (ruff, ty, uv, complexipy) with the bumped pyproject versions. - Regenerate uv.lock and pylock.toml. CI runner references were already on zhuiri/suanni; no container/registry publishing applies (no Containerfile).
🔧 chore: finish forge stage-2 migration and bump dependencies
All checks were successful
/ gitleaks (pull_request) Successful in 51s
Details
/ pr-review (pull_request) Successful in 2m32s
Details
/ checks (pull_request) Successful in 2m52s
Details
/ publish (pull_request) Has been skipped
Details
/ deploy-docs (pull_request) Has been skipped
Details
ca6a5962ad
forgejo-actions reviewed 2026-08-18 23:29:16 +00:00
forgejo-actions left a comment
Copy link

WuMing

Found 4 issue(s). See inline comments below.

## WuMing Found **4** issue(s). See inline comments below.
.pre-commit-config.yaml
@ -12,3 +12,3 @@
- repo: https://github.com/astral-sh/ruff-pre-commit
rev: v0.16.1
rev: v0.16.2
forgejo-actions commented 2026-08-18 23:29:16 +00:00
Copy link

config [MEDIUM]

Pre-commit ruff rev is pinned to v0.16.2, but uv.lock/pylock.toml resolved ruff to 0.16.3. This means pre-commit and uv run ruff may use different versions; update the rev to v0.16.3 or otherwise align the exact versions.

**config** [MEDIUM] Pre-commit ruff rev is pinned to v0.16.2, but uv.lock/pylock.toml resolved ruff to 0.16.3. This means pre-commit and `uv run ruff` may use different versions; update the rev to v0.16.3 or otherwise align the exact versions. <!-- wuming:sha256:239d1c20aa74d63c49c54b8981e0dfe70d42c3e0c118c57d58582c4791666149 -->
marvin8 marked this conversation as resolved
.pre-commit-config.yaml
@ -22,3 +22,3 @@
- repo: https://github.com/astral-sh/ty-pre-commit
rev: v0.0.69
rev: v0.0.70
forgejo-actions commented 2026-08-18 23:29:16 +00:00
Copy link

config [MEDIUM]

Pre-commit ty rev is pinned to v0.0.70, but uv.lock/pylock.toml resolved ty to 0.0.72. Update the rev to v0.0.72 so pre-commit and the locked dev environment use the same ty version.

**config** [MEDIUM] Pre-commit ty rev is pinned to v0.0.70, but uv.lock/pylock.toml resolved ty to 0.0.72. Update the rev to v0.0.72 so pre-commit and the locked dev environment use the same ty version. <!-- wuming:sha256:a4ca3b0e77a75012b53b93f1c735d52d7a6ef2c2788836854cfa930b89ea8c21 -->
marvin8 marked this conversation as resolved
.pre-commit-config.yaml
@ -27,3 +27,3 @@
- repo: https://github.com/astral-sh/uv-pre-commit
rev: 0.12.2
rev: 0.12.3
forgejo-actions commented 2026-08-18 23:29:16 +00:00
Copy link

config [MEDIUM]

Pre-commit uv rev is pinned to 0.12.3, but uv.lock/pylock.toml resolved uv to 0.12.5. Update the rev to 0.12.5 so the uv-pre-commit hooks operate on the same uv version that generated the lockfile.

**config** [MEDIUM] Pre-commit uv rev is pinned to 0.12.3, but uv.lock/pylock.toml resolved uv to 0.12.5. Update the rev to 0.12.5 so the uv-pre-commit hooks operate on the same uv version that generated the lockfile. <!-- wuming:sha256:34a7a14fda94df1c256b53e7017b8061eb890816ecd04044fcded97c48aa5f9e -->
marvin8 marked this conversation as resolved
.pre-commit-config.yaml
@ -39,3 +39,3 @@
- repo: https://github.com/rohaquinlop/complexipy-pre-commit
rev: v5.1.0 # Use the latest version
rev: v7.0.0 # Use the latest version
forgejo-actions commented 2026-08-18 23:29:16 +00:00
Copy link

config [MEDIUM]

Pre-commit complexipy rev is pinned to v7.0.0, but uv.lock/pylock.toml resolved complexipy to 7.0.1. Update the rev to v7.0.1 (if the complexipy-pre-commit repo publishes that tag) so the hook and the locked dev dependency versions match.

**config** [MEDIUM] Pre-commit complexipy rev is pinned to v7.0.0, but uv.lock/pylock.toml resolved complexipy to 7.0.1. Update the rev to v7.0.1 (if the complexipy-pre-commit repo publishes that tag) so the hook and the locked dev dependency versions match. <!-- wuming:sha256:f65827fe9de4c2a33824a5c638db35c3f97c466f76863503dcef9ee104f5751c -->
marvin8 marked this conversation as resolved
agent-pi commented 2026-08-19 00:01:46 +00:00
Author
Collaborator
Copy link

🔴 Not actioned — pre-commit revs intentionally match the ~= spec

.pre-commit-config.yaml line 14 · .pre-commit-config.yaml line 24 · .pre-commit-config.yaml line 29 · .pre-commit-config.yaml line 41

Pre-commit hook revs are pinned one patch behind the resolved lockfile versions.

Declined: the pre-commit rev: matches the ~= spec chosen at bump time. The lock's newer patch is still inside zaojun's 7-day supply-chain quarantine, so bumping the rev up would adopt a quarantined version. Per AGENTS.md: "uv sync may resolve a newer patch within the ~= range — that is fine… the pre-commit rev does not need to match the installed version exactly."

### 🔴 Not actioned — pre-commit revs intentionally match the `~=` spec [`.pre-commit-config.yaml` line 14](https://forge.marvin8.zone/marvin8/sub2pod/pulls/25#issuecomment-1600) · [`.pre-commit-config.yaml` line 24](https://forge.marvin8.zone/marvin8/sub2pod/pulls/25#issuecomment-1601) · [`.pre-commit-config.yaml` line 29](https://forge.marvin8.zone/marvin8/sub2pod/pulls/25#issuecomment-1602) · [`.pre-commit-config.yaml` line 41](https://forge.marvin8.zone/marvin8/sub2pod/pulls/25#issuecomment-1603) > Pre-commit hook revs are pinned one patch behind the resolved lockfile versions. Declined: the pre-commit `rev:` matches the `~=` spec chosen at bump time. The lock's newer patch is still inside zaojun's 7-day supply-chain quarantine, so bumping the rev up would adopt a quarantined version. Per AGENTS.md: "uv sync may resolve a newer patch within the `~=` range — that is fine… the pre-commit rev does not need to match the installed version exactly."
marvin8 approved these changes 2026-08-19 00:28:40 +00:00
marvin8 manually merged commit c96f63846c into main 2026-08-19 00:29:34 +00:00
marvin8 deleted branch chore/stage2-migration 2026-08-19 00:30:22 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
marvin8
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
marvin8/sub2pod!25
No description provided.