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

Finalise stage-2 migration to forge.marvin8.zone #18

Manually merged
marvin8 merged 2 commits from chore/stage2-migration into main 2026-08-19 00:36:59 +00:00
Conversation 3 Commits 2 Files changed 5 +288 -288
agent-pi commented 2026-08-18 23:26:46 +00:00
Collaborator
Copy link

Stage-2 migration cleanup for rainlog.

  • Update pre-commit zaojun repo URL from codeberg.org to forge.marvin8.zone
  • Update CLAUDE.md release wording (Codeberg links → forge.marvin8.zone links)
  • Remove local claude remote
  • Bump dependencies: cyclopts, platformdirs, bump-my-version, complexipy, prek, ruff, ty
  • Align pre-commit hook revs (ruff v0.16.2, ty v0.0.70, complexipy v7.0.0)
  • pysentry: 0 vulnerabilities found
  • Checks green: ruff check, ruff format --check, ty check, complexipy, nox -s pytest (5 Python versions)
Stage-2 migration cleanup for rainlog. - Update pre-commit zaojun repo URL from codeberg.org to forge.marvin8.zone - Update CLAUDE.md release wording (Codeberg links → forge.marvin8.zone links) - Remove local claude remote - Bump dependencies: cyclopts, platformdirs, bump-my-version, complexipy, prek, ruff, ty - Align pre-commit hook revs (ruff v0.16.2, ty v0.0.70, complexipy v7.0.0) - pysentry: 0 vulnerabilities found - Checks green: ruff check, ruff format --check, ty check, complexipy, nox -s pytest (5 Python versions)
🔧 finalise stage-2 migration and bump dependencies
Some checks failed
/ gitleaks (pull_request) Successful in 20s
Details
/ pr-review (pull_request) Successful in 2m28s
Details
/ checks (pull_request) Failing after 4m22s
Details
/ publish (pull_request) Has been skipped
Details
/ deploy-docs (pull_request) Has been skipped
Details
67d00e90a8
forgejo-actions reviewed 2026-08-18 23:29:13 +00:00
forgejo-actions left a comment
Copy link

WuMing

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

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

config [MEDIUM]

Pre-commit ruff rev is pinned to v0.16.2 while pylock.toml resolves ruff to 0.16.3. This means the pre-commit hook can produce different results from the locked/locally installed toolchain. Update the rev to v0.16.3, or pin the lock to v0.16.2, so the versions match.

**config** [MEDIUM] Pre-commit ruff rev is pinned to v0.16.2 while pylock.toml resolves ruff to 0.16.3. This means the pre-commit hook can produce different results from the locked/locally installed toolchain. Update the rev to v0.16.3, or pin the lock to v0.16.2, so the versions match. <!-- wuming:sha256:66d7efdf4bbe96dfb442297fde33671e0648e512ad6fa1fc439c39f8ddcb0477 -->
marvin8 marked this conversation as resolved
.pre-commit-config.yaml
@ -24,3 +24,3 @@
- repo: https://github.com/astral-sh/ty-pre-commit
rev: v0.0.65
rev: v0.0.70
forgejo-actions commented 2026-08-18 23:29:13 +00:00
Copy link

config [MEDIUM]

Pre-commit ty rev is pinned to v0.0.70 while pylock.toml resolves ty to 0.0.72. Align the hook rev to v0.0.72 to match the version used by the other ty checks, or pin the lock to v0.0.70.

**config** [MEDIUM] Pre-commit ty rev is pinned to v0.0.70 while pylock.toml resolves ty to 0.0.72. Align the hook rev to v0.0.72 to match the version used by the other ty checks, or pin the lock to v0.0.70. <!-- wuming:sha256:852bb2f7e215bdc98d1090b75c9ae2d45451bc0433ccce6b44c669eccfa65234 -->
marvin8 marked this conversation as resolved
.pre-commit-config.yaml
@ -41,3 +41,3 @@
- repo: https://github.com/rohaquinlop/complexipy-pre-commit
rev: v5.1.0
rev: v7.0.0
forgejo-actions commented 2026-08-18 23:29:13 +00:00
Copy link

config [MEDIUM]

Pre-commit complexipy rev is pinned to v7.0.0 while pylock.toml resolves complexipy to 7.0.1. Update the hook rev to v7.0.1, or pin the lock to v7.0.0, so pre-commit and the development environment use the same version.

**config** [MEDIUM] Pre-commit complexipy rev is pinned to v7.0.0 while pylock.toml resolves complexipy to 7.0.1. Update the hook rev to v7.0.1, or pin the lock to v7.0.0, so pre-commit and the development environment use the same version. <!-- wuming:sha256:99486f46e6adb5a13c577b7c9e4105b7c9c1026eb4b4952cfe9b47feb4e88ecc -->
marvin8 marked this conversation as resolved
🔧 Re-trigger CI after transient zaojun segfault
All checks were successful
/ gitleaks (pull_request) Successful in 16s
Details
/ pr-review (pull_request) Successful in 1m48s
Details
/ checks (pull_request) Successful in 4m6s
Details
/ publish (pull_request) Has been skipped
Details
/ deploy-docs (pull_request) Has been skipped
Details
7fa2910617
agent-pi commented 2026-08-19 00:01:42 +00:00
Author
Collaborator
Copy link

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

.pre-commit-config.yaml line 43 · .pre-commit-config.yaml line 16 · .pre-commit-config.yaml line 26

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 43](https://forge.marvin8.zone/marvin8/rainlog/pulls/18#issuecomment-1598) · [`.pre-commit-config.yaml` line 16](https://forge.marvin8.zone/marvin8/rainlog/pulls/18#issuecomment-1596) · [`.pre-commit-config.yaml` line 26](https://forge.marvin8.zone/marvin8/rainlog/pulls/18#issuecomment-1597) > 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:36:31 +00:00
marvin8 manually merged commit 52891f71b7 into main 2026-08-19 00:36:59 +00:00
marvin8 deleted branch chore/stage2-migration 2026-08-19 00:37:47 +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/rainlog!18
No description provided.