Skip to content

chore: pin-freshness audit found 13 stale pin(s) #84

@github-actions

Description

@github-actions

The weekly pin-freshness audit flagged 13 stale pin(s).

See the run log for the per-pin annotations: https://github.com/constk/harness-python-react/actions/runs/25305846760

Each finding is one of:

  • Tag pin no longer resolves — upstream tag was deleted or renamed; bump to a current tag or SHA pin per docs/DEVELOPMENT.md#action-pinning-policy.
  • SHA pin: documented tag re-tagged — the trailing # vN.M.P comment names a tag that now points at a different SHA upstream. Either bump the pin to the new SHA (preferred) or update the comment to a tag that still matches.
  • API failure — couldn't reach the upstream registry; transient, will likely clear on the next weekly run.

Closes when the offending pin is updated and the next audit run is clean.

Metadata

Metadata

Assignees

No one assigned

    Labels

    harnessCross-cutting harness mechanics (controls, hooks, gates)securitySecurity scanning, secrets, vulns

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions