Skip to content

ci: fix automerge for yarn repo - #278

Merged
rvwatch merged 1 commit into
mainfrom
fix/automerge-yarn-cache
Sep 14, 2026
Merged

rvwatch merged 1 commit into
mainfrom
fix/automerge-yarn-cache

Conversation

@rvwatch

@rvwatch rvwatch commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

What

The scheduled automerge workflow has been failing every run (see recent failure emails). It calls the shared salesforcecli/github-workflows/.github/workflows/automerge.yml@main, which:

  1. Defaults setup-node caching to npm (cache-dependency-path: package-lock.json). This repo is yarn — no package-lock.json — so setup-node dies with Some specified paths were not resolved, unable to cache dependencies in ~5s, before the merge step ever runs.
  2. Defaults mergeMethod: merge. This repo's branch ruleset only allows squash/rebase, so even a fixed cache would fail at merge.

Fix

Pass the shared workflow's existing inputs:

  • package-manager: yarn
  • cache-dependency-path: yarn.lock
  • mergeMethod: squash

No fork/pin — keeps receiving upstream fixes.

Effect

Restores unattended automerge of dependabot PRs, stopping the manual approve/--admin merges and the failed-run emails.

[skip-validate-pr]

The automerge workflow calls the shared salesforcecli/github-workflows
automerge, which defaulted to npm caching (package-lock.json) and merge
commits. This repo uses yarn and a branch ruleset that only allows
squash/rebase, so every scheduled run failed at setup-node and the merge
step. Pass yarn/yarn.lock and mergeMethod: squash.
@github-actions

Copy link
Copy Markdown

This PR lacks any commits of the 'fix' or 'feat' type, and therefore will not trigger a release. To silence all further warnings, react to this warning comment (or any other) with the 👀 emoji.

NOTE: If your repo uses squash commits, make sure to add the appropriate conventional commit prefix (e.g., 'fix:', 'feat:', 'chore:', etc) in the squash commit message.

@rvwatch
rvwatch merged commit 172696d into main Sep 14, 2026
18 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant