Bump WuMing to 0.12.0 and floor review findings at medium severity #19
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
3 participants
Notifications
Due date
No due date set.
Reference
marvin8/xique!19
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/issue-18-wuming-0.12.0-medium-floor"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
pr-reviewjob now tracks WuMing 0.12.0 and setsWUMING_MIN_SEVERITY: medium, so only medium-and-above findings are posted as inline review comments.The severity floor is set via a step-level
env:block because 0.12.0 still has nomin_severityaction input (verified againstaction.ymlat ref0.12.0on the forge).Closes #18
WuMing
Found 1 issue(s). See inline comments below.
@ -18,3 +18,3 @@if: github.event_name == 'pull_request'steps:- uses: https://forge.marvin8.zone/marvin8/wuming@0.11.0- uses: https://forge.marvin8.zone/marvin8/wuming@0.12.0security [HIGH]
Use of mutable version tag for third-party action violates supply chain integrity. Pin to a commit hash to prevent tampering and ensure reproducible builds. (A08: Software and Data Integrity Failures)
.forgejo/workflows/ci.ymlline 20🔴 Declined — version-tag pinning of
marvin8/wumingis a deliberate fleet-wide decision (standing precedent from the Oct 2026 OpenRouter migration, declined identically on the rainlog/zaojun/feed2fedi PRs): wuming is a first-party action on the same forge, owned by the same account as this repo, so the A08 tag-tampering threat model would require an account compromise that owns this repository anyway. The rest of the workflow (actions/checkout@v4,astral-sh/setup-uv@v5) follows the same convention.