Repository navigation
fix(ci): lock smtp-notify-action at v0.5.0 to match the workflow - #112
Conversation
Dependabot #106 bumped push-email-notify.yml to hyperpolymath/smtp-notify-action@v0.5.0 but left actions.lock pinning v0.3.0, so the lock-sync gate has failed on main since. Regenerated with `gh actions-lock`: the v0.5.0 entry resolves to commit c1c9fa07 and the unused v0.3.0 entry is dropped. No other entry changes. Closes #108 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016XJoh8YA2sCWQmq93CF8RX
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
|



Summary
Closes #108.
Dependabot #106 moved
.github/workflows/push-email-notify.ymltohyperpolymath/smtp-notify-action@v0.5.0but leftactions.lockpinningv0.3.0. Since then, the checkactions.lock is in sync with the workflow YAMLhas failed onmainand on every PR. This PR regenerates the lockfile so it matches the workflow, and changes nothing else.Type of change
CI lockfile sync. No workflow, registry or package content changes.
📌 New pins
Head SHA: 8239999
actions.lock:hyperpolymath/smtp-notify-action@v0.5.0→sha1-c1c9fa07992a02c1fd3d67a0dc1b08cccb852aef. This is the commit thev0.5.0tag peels to (git ls-remote … refs/tags/v0.5.0^{}), not the tag objectc6a2a6dc.hyperpolymath/smtp-notify-action@v0.3.0→sha1-22e7bdb3…. No workflow references it any more.using: compositeat v0.5.0 with no nesteduses:, so it adds no transitive pins.Changes
.github/workflows/actions.lock: in thepush-email-notify.ymllist and thedependencies:table,v0.3.0→v0.5.0. Generated bygh actions-lock, not hand-edited.RSR Quality Checklist
Required
actions.lockis a machine-generated file that has never carried a header, and no source file is touched..envfiles included.actions.lock is in sync with the workflow YAMLgreen. The twogovernancereds onmain(Workflow security linter,Allowlist Preflight) are deferred to CI: governance linter calls a missing scripts/update-actions-lock.sh; Allowlist Preflight runs with an empty GH_TOKEN #105 and unaffected by this PR.As Applicable — Registry Changes
Registry.toml: not applicable, no package or version changes.As Applicable — Documentation / Infra Changes
.machine_readable/6a2/*.a2ml: not applicable. A2ML is retired estate-wide (D99, D269c).TOPOLOGY.md: not applicable, no architecture change.CHANGELOG.md: not touched. The commit is a conventionalfix(ci):.Testing
gh actions-lock --no-fixonorigin/main(4141456): fails withworkflow uses ref "v0.5.0" but lockfile pins "v0.3.0"andUnused lockfile entry hyperpolymath/smtp-notify-action@v0.3.0. On this head it exits 0.bash scripts/check-lock-sync.shon this head exits 0. It confirms everyuses:is locked under its own workflow path, every lockfile entry is still referenced, 0 dangling edges, and every workflow file has a lockfile key.gh actions-lockalso tried to prepend itsmanaged by gh actions-lockheader tolock-sync-gate.yml. That edit was reverted to keep this PR lock-only, and--no-fixstill exits 0 without it.git log --format=%G?→G(SSH-signed).Deferred red checks
Both checks are red on
maintoo. This PR does not touch them.governance / Workflow security linter: deferred to CI: governance linter calls a missing scripts/update-actions-lock.sh; Allowlist Preflight runs with an empty GH_TOKEN #105. The linter calls a missingscripts/update-actions-lock.sh.governance / Allowlist Preflight: deferred to CI: governance linter calls a missing scripts/update-actions-lock.sh; Allowlist Preflight runs with an empty GH_TOKEN #105. It runs with an emptyGH_TOKEN.Merge
Squash. Auto-merge is not armed; this registry PR is for the owner's review.
🤖 Generated with Claude Code
https://claude.ai/code/session_016XJoh8YA2sCWQmq93CF8RX