Skip to content

chore(deps): update ferrlabs/.github digest to 84f4447 - #340

Open
ferrlabs-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/ferrlabs-actions
Open

chore(deps): update ferrlabs/.github digest to 84f4447#340
ferrlabs-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/ferrlabs-actions

Conversation

@ferrlabs-renovate

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
FerrLabs/.github (changelog) workflow digest 539e9ac84f4447

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@ferrlabs-renovate
ferrlabs-renovate Bot enabled auto-merge (squash) September 7, 2026 12:14
Comment thread .github/workflows/ci.yml
packages: read
name: Test
uses: FerrLabs/.github/.github/workflows/reusable-ci-node.yml@539e9aca37e08abde8d9cefbe13cd98fa62b1b41 # main
uses: FerrLabs/.github/.github/workflows/reusable-ci-node.yml@84f44470a9ff640ea8bb32efc74d45f912660d71 # main
Comment thread .github/workflows/ci.yml
contents: write
id-token: write
uses: FerrLabs/.github/.github/workflows/reusable-ferrflow-release.yml@539e9aca37e08abde8d9cefbe13cd98fa62b1b41 # main
uses: FerrLabs/.github/.github/workflows/reusable-ferrflow-release.yml@84f44470a9ff640ea8bb32efc74d45f912660d71 # main
jobs:
dispatch:
uses: FerrLabs/.github/.github/workflows/reusable-renovate-dispatch.yml@539e9aca37e08abde8d9cefbe13cd98fa62b1b41 # main
uses: FerrLabs/.github/.github/workflows/reusable-renovate-dispatch.yml@84f44470a9ff640ea8bb32efc74d45f912660d71 # main
scan:
name: Secrets + CVE
uses: FerrLabs/.github/.github/workflows/reusable-security-scan.yml@539e9aca37e08abde8d9cefbe13cd98fa62b1b41 # main
uses: FerrLabs/.github/.github/workflows/reusable-security-scan.yml@84f44470a9ff640ea8bb32efc74d45f912660d71 # main
@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

SonarQube — aucune nouvelle issue

Comparaison entre le projet bac à sable de cette PR et la branche par défaut : SonarQube Community n'analyse pas les PR, ce delta est calculé côté CI. Détail

@ferrfleet ferrfleet Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What changed: the only substantive commit in this digest range (FerrLabs/.github 539e9ac → 84f4447, #335) changes reusable-ci-node.yml's pnpm-version input default from '10' to ''. Empty now means pnpm/action-setup reads the pnpm version from the caller's package.json (packageManager or devEngines.packageManager) instead of hardcoding v10.

What breaks here: this repo's package.json has no packageManager field, only engines.pnpm: ">=9.0.0" (a range, not an exact pin), which pnpm/action-setup doesn't read. That's exactly why CI is failing.

Why CI fails: Test / Test & Build and Test / Quality (knip, madge, audit) both fail at the pnpm/action-setup step with: "Unable to determine pnpm version... provide it via the action's version input, or package.json's packageManager / devEngines.packageManager field." This is a real incompatibility introduced by the upstream default change, not a flake or a pre-existing failure.

Blocking: add a packageManager field to package.json (e.g. "packageManager": "pnpm@9.x.x", matching whatever pnpm version this repo currently builds with) before merging, or this and every future PR will fail CI until that's done.

@ferrlabs-renovate
ferrlabs-renovate Bot force-pushed the renovate/ferrlabs-actions branch from ee8285c to dc746a5 Compare September 8, 2026 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant