Jamie Tanna 64aa6497b9 fix(manager/github-actions): relock when regenerating actions.lock (#47294) ...

As noted in #47292, since `gh actions-lock` v0.2.0 locked pins are
sticky: running `gh actions-lock` only resolves refs that the lockfile
doesn't record yet.

If a ref updates (i.e. `pnpm/setup@v3.0.0` to `pnpm/setup@v3.1.1`), then
`gh actions-lock` fails with a `Ref changed` error and `Unused lockfile
entry`, and writes nothing out, leaving the branch in an unusable state.

Per v0.2.0's release notes, we should use `--relock` to re-resolve every
ref and rebuilds the lockfile graph.

This updates floating tags i.e. `@v4` when occurring, because they are
technically a floating tag that has now updated.

Co-authored-by: Claude Sonnet 5.5 <jamie.tanna+claude-code@mend.io>

2026-10-22 08:01:28 +00:00

..

datasource

fix(workers): keep URL credentials of dependencies out of the repository cache and generated texts

2026-10-20 09:05:00 +01:00

manager

fix(manager/github-actions): relock when regenerating actions.lock (#47294)

2026-10-22 08:01:28 +00:00

platform

fix(platform/azure): apply the repo's azureWorkItemType (#47158)

2026-10-19 12:32:56 +00:00

versioning

refactor(versioning/gomod): parse the commit of pseudo-versions (#47097)

2026-10-16 09:52:08 +00:00