chore(release): bump packslip action to v1.0.0 - #95
Conversation
v1.0.0 declares the manifest format stable, fixes the packslip.dev/releases/v1 predicate URL that previously 404d, and enforces a format on every artifact (archives already carry one via their file name, so this repository needs no other change). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe release workflow updates the ChangesRelease signing
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to Release asset signing now uses packslip v1.0.1 with unchanged workflow inputs. The supplied compatibility evidence indicates the release artifacts remain supported, with no current merge-blocking risk. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Greptile SummaryUpdates the commit-pinned
Confidence Score: 5/5The PR appears safe to merge because the narrowly scoped action update preserves the established release-attestation contract. No actionable failures or outstanding repository-rule violations were identified in the updated workflow. Important Files Changed
Reviews (2): Last reviewed commit: "chore(release): bump packslip action to ..." | Re-trigger Greptile |
v1.0.1 carries the fixes from jdx/packslip#63 and #65, along with the new download input from #69 (not adopted here -- this workflow already assembles release archives from an internal workflow artifact rather than gh release download, so download would not remove a step).
Instruction countsNothing was compared, and so nothing was gated. No series appears on both sides: either the base has no measurements recorded, or the two were measured on different runner classes, which are deliberately not comparable — counts shift between machine types by more than a real regression does. New, nothing to compare against: Only instruction counts gate. Wall clock is shown for context — on identical hardware it moves 4-20% run to run. Measured by tak — instruction-counted CLI benchmarks, stored in this repository's git notes.
|
Summary
jdx/packslipaction from v0.3.0 to v1.0.0.packslip.dev/releases/v1predicate URL that previously 404d, and requires every artifact to declare a format (already satisfied here — every artifact is an archive, which infers its format from the file name).Test plan
packslip.sigstore.json🤖 Generated with Claude Code
Note
Low Risk
Single CI dependency pin in the release attach job; no application or auth logic changes, with existing artifact globs already compatible with v1 format requirements.
Overview
Updates the release workflow’s pinned
jdx/packslipstep from v0.3.0 to v1.0.1 (commita6eddff…). Inputs (tag,artifacts,bin) are unchanged; only the action reference in the attach job moves forward.This picks up the v1 manifest/stable format behavior and predicate URL fixes described for the v1 line, without changing how binaries are built or uploaded—packslip still runs after assets are attached to the tag.
Reviewed by Cursor Bugbot for commit 89e884c. Bugbot is set up for automated code reviews on this repo. Configure here.
AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5; version: unavailable.
Summary by CodeRabbit