ci(deps): bump the github-actions group across 1 directory with 4 updates

[dependabot]

Bumps the github-actions group with 4 updates in the / directory: pnpm/action-setup, actions/setup-node, github/codeql-action and slackapi/slack-github-action.

Updates pnpm/action-setup from 5.0.0 to 6.0.4

Release notes

Sourced from pnpm/action-setup's releases.

v6.0.4

What's Changed

• fix: use npm co-located with the action node binary by @​benquarmby in pnpm/action-setup#239

New Contributors

• @​benquarmby made their first contribution in pnpm/action-setup#239

Full Changelog: pnpm/action-setup@v6.0.3...v6.0.4

v6.0.3

Updated pnpm to v11.0.0-rc.5

Full Changelog: pnpm/action-setup@v6.0.2...v6.0.3

v6.0.2

What's Changed

• fix: pnpm self-update binary shadowed by bootstrap on PATH by @​oniani1 in pnpm/action-setup#230

New Contributors

• @​oniani1 made their first contribution in pnpm/action-setup#230

Full Changelog: pnpm/action-setup@v6.0.1...v6.0.2

v6.0.1

Update pnpm to v11.0.0-rc.2. pnpm-lock.yaml will not be saved with two documents unless the packageManager is set via devEngines.packageManager. Related issue: pnpm/action-setup#228

v6.0.0

Added support for pnpm v11.

Commits

• 26f6d4f fix: use npm co-located with the action node binary (#239)
• 903f9c1 fix: update pnpm to 11.0.0-rc.5
• bdf0af2 test: add strict version-match jobs to reproduce #225 / #227
• 71c9247 fix: pnpm self-update binary shadowed by bootstrap on PATH (#230)
• 078e9d4 fix: update pnpm to 11.0.0-rc.2
• 08c4be7 docs(README): update action-setup version
• 5798914 chore: update .gitignore
• ddffd66 fix: remove accidentally committed file
• b43f991 fix: update pnpm to 11.0.0-rc.0
• 3852509 README.md: bring versions up-to-date (#222)
• Additional commits viewable in compare view

Updates actions/setup-node from 6.3.0 to 6.4.0

Release notes

Sourced from actions/setup-node's releases.

v6.4.0

What's Changed

Dependency updates:

• Upgrade @​actions dependencies by @​Copilot in actions/setup-node#1525
• Update Node.js versions in versions.yml and bump package to v6.4.0 by @​priya-kinthali in actions/setup-node#1533

New Contributors

• @​Copilot made their first contribution in actions/setup-node#1525

Full Changelog: actions/setup-node@v6...v6.4.0

Commits

• 48b55a0 Update Node.js versions in versions.yml and bump package to v6.4.0 (#1533)
• ab72c7e Upgrade @​actions dependencies (#1525)
• See full diff in compare view

Updates github/codeql-action from 4.35.1 to 4.35.3

Release notes

Sourced from github/codeql-action's releases.

v4.35.3

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.19.3 and earlier. These versions of CodeQL were discontinued on 9 April 2026 alongside GitHub Enterprise Server 3.15, and will be unsupported by the next minor release of the CodeQL Action. #3837
• Configurations for private registries that use Cloudsmith or GCP OIDC are now accepted. #3850
• Best-effort connection tests for private registries now use GET requests instead of HEAD for better compatibility with various registry implementations. For NuGet feeds, the test is now always performed against the service index. #3853
• Fixed a bug where two diagnostics produced within the same millisecond could overwrite each other on disk, causing one of them to be lost. #3852
• Update default CodeQL bundle version to 2.25.3. #3865

v4.35.2

• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable is deprecated and will be removed in May 2026. If you are affected by this, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #3795
• The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #3789
• Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. #3794
• Fixed a bug in the validation of OIDC configurations for private registries that was added in CodeQL Action 4.33.0 / 3.33.0. #3807
• Update default CodeQL bundle version to 2.25.2. #3823

Changelog

Sourced from github/codeql-action's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

• Update default CodeQL bundle version to 2.25.4. #3881

4.35.3 - 01 May 2026

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.19.3 and earlier. These versions of CodeQL were discontinued on 9 April 2026 alongside GitHub Enterprise Server 3.15, and will be unsupported by the next minor release of the CodeQL Action. #3837
• Configurations for private registries that use Cloudsmith or GCP OIDC are now accepted. #3850
• Best-effort connection tests for private registries now use GET requests instead of HEAD for better compatibility with various registry implementations. For NuGet feeds, the test is now always performed against the service index. #3853
• Fixed a bug where two diagnostics produced within the same millisecond could overwrite each other on disk, causing one of them to be lost. #3852
• Update default CodeQL bundle version to 2.25.3. #3865

4.35.2 - 15 Apr 2026

• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable is deprecated and will be removed in May 2026. If you are affected by this, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #3795
• The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #3789
• Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. #3794
• Fixed a bug in the validation of OIDC configurations for private registries that was added in CodeQL Action 4.33.0 / 3.33.0. #3807
• Update default CodeQL bundle version to 2.25.2. #3823

4.35.1 - 27 Mar 2026

• Fix incorrect minimum required Git version for improved incremental analysis: it should have been 2.36.0, not 2.11.0. #3781

4.35.0 - 27 Mar 2026

• Reduced the minimum Git version required for improved incremental analysis from 2.38.0 to 2.11.0. #3767
• Update default CodeQL bundle version to 2.25.1. #3773

4.34.1 - 20 Mar 2026

• Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #3762

4.34.0 - 20 Mar 2026

• Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #3569
• We are rolling out improved incremental analysis to C/C++ analyses that use build mode none. We expect this rollout to be complete by the end of April 2026. #3584
• Update default CodeQL bundle version to 2.25.0. #3585

4.33.0 - 16 Mar 2026

• Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562

  To opt out of this change:

  • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.

... (truncated)

Commits

• e46ed2c Merge pull request #3867 from github/update-v4.35.3-8c6e48dbe
• b73d1d1 Add changelog entry for #3853
• 24e0bb0 Reorder changelog entries
• ec298da Update changelog for v4.35.3
• 8c6e48d Merge pull request #3865 from github/update-bundle/codeql-bundle-v2.25.3
• 7190983 Add changelog note
• 2bb2095 Update default bundle to codeql-bundle-v2.25.3
• 7851e55 Merge pull request #3850 from github/mbg/private-registry/cloudsmith-gcp
• 262a15f Add generic non-printable chars test for OIDC configs
• a6109b1 Merge pull request #3853 from github/mbg/start-proxy/improved-checks
• Additional commits viewable in compare view

Updates slackapi/slack-github-action from 3.0.1 to 3.0.3

Release notes

Sourced from slackapi/slack-github-action's releases.

Slack GitHub Action v3.0.3

Patch Changes

• 66834e4: feat: add instrumentation to address error rates

Slack GitHub Action v3.0.2

Patch Changes

• 79529d7: fix: resolve url.parse deprecation warning for webhook techniques

Changelog

Sourced from slackapi/slack-github-action's changelog.

slack-github-action

3.0.3

Patch Changes

• 66834e4: feat: add instrumentation to address error rates

3.0.2

Patch Changes

• 79529d7: fix: resolve url.parse deprecation warning for webhook techniques

Commits

• 45a88b9 chore: release
• 1c0bcf0 chore: release (#606)
• 66834e4 feat: add instrumentation to address error rates (#600)
• 0fe0f90 build(deps): bump @​actions/github from 9.0.0 to 9.1.1 (#605)
• c5e7059 build(deps): bump @​slack/web-api from 7.15.0 to 7.15.1 (#604)
• 0325526 build(deps-dev): bump @​biomejs/biome from 2.4.10 to 2.4.13 (#601)
• 900cd3e build(deps-dev): bump @​types/node from 24.12.0 to 24.12.2 (#603)
• 53fdcff build(deps): bump @​actions/core from 3.0.0 to 3.0.1 (#602)
• 26856cc build(deps): bump slackapi/slack-github-action from 3.0.1 to 3.0.2 (#596)
• feba1e2 ci: skip publish step if no release is needed (#599)
• Additional commits viewable in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
langfuse-js	Ready	Preview	May 8, 2026 5:23am

[claude]

🔴 The bump of pnpm/action-setup from v5.0.0 to v6.0.3 directly contradicts the explicit # Pin to v5 — v6 uses pnpm v11 internally which mutates the lockfile comment (referencing pnpm/action-setup#228) that sits immediately above each of the 4 occurrences (ci.yml lines 31, 62, 161 and release.yml line 75). v6.0.3 ships pnpm v11.0.0-rc.5 (a release candidate), and the lint job's Verify lockfile integrity step (git diff --exit-code pnpm-lock.yaml) — which was added precisely to catch this — will fail if pnpm 11 mutates the lockfile generated by the pinned packageManager: pnpm@10.33.0. Either revert this dependency to v5 (and add a Dependabot ignore for the v6 major), or, if the upgrade is intentional and verified, remove the now-misleading "Pin to v5" comments and confirm the lockfile-integrity check still passes.

Extended reasoning...

What the bug is

The PR upgrades pnpm/action-setup from v5.0.0 to v6.0.3 in 4 places, but leaves intact the explicit pinning guard immediately above each occurrence:

# Pin to v5 — v6 uses pnpm v11 internally which mutates the lockfile
# https://github.com/pnpm/action-setup/issues/228
- uses: pnpm/action-setup@903f9c1a6ebcba6cf41d87230be49611ac97822e # v6.0.3

This is a self-contradicting state: the comment tells future contributors not to bump to v6 because of a known lockfile-mutation issue, yet the very next line is now pinned to v6. The four affected locations are:

• .github/workflows/ci.yml line 31 (test-integration job)
• .github/workflows/ci.yml line 62 (test-e2e job)
• .github/workflows/ci.yml line 161 (lint job)
• .github/workflows/release.yml line 75 (release-js-sdk job)

Why this is risky in this repo specifically

The lint job in ci.yml has a hard guard that was added in the same change that introduced the Pin to v5 comments:

- name: Verify lockfile integrity
  run: |
    git diff --exit-code pnpm-lock.yaml || {
      echo "❌ Error: pnpm-lock.yaml was modified during install"
      exit 1
    }

The release workflow has the same guard. package.json pins packageManager: pnpm@10.33.0 (top-level, not devEngines.packageManager). The pnpm/action-setup v6.0.1 release notes explicitly state:

pnpm-lock.yaml will not be saved with two documents unless the packageManager is set via devEngines.packageManager.

So the v6.0.1 fix is conditional on a devEngines.packageManager configuration that this repo does not use. The repo's configuration is precisely the layout that originally tripped issue #228. Whether the v6 self-update path still leaves the lockfile clean for top-level packageManager users is unverified by this PR.

Step-by-step proof of impact

1. CI starts the lint job on a checkout where pnpm-lock.yaml was generated by pnpm v10.33.0.
2. pnpm/action-setup@v6.0.3 runs. Per the action's release notes, it bootstraps pnpm v11 (specifically v11.0.0-rc.5, a release candidate) and may then self-update.
3. pnpm install --frozen-lockfile runs under pnpm 11. If pnpm 11 rewrites pnpm-lock.yaml (lockfile format, internal sort order, integrity hashes, or the dual-document layout from chore(deps-dev): bump @babel/preset-typescript from 7.24.1 to 7.24.7 #228) the file becomes dirty in the working tree.
4. The next step runs git diff --exit-code pnpm-lock.yaml. If the file changed, exit code is non-zero and the job fails with "❌ Error: pnpm-lock.yaml was modified during install".
5. Because all-tests-passed aggregates needs: [test-e2e, test-integration, lint] with if: contains(needs.*.result, 'failure'), the entire CI gate fails.

Even in the optimistic case where v6.0.3 happens not to mutate the lockfile in this configuration, point #3 introduces a release candidate (pnpm v11.0.0-rc.5) into the release pipeline — a stability regression for tooling that publishes to npm.

Why the existing code doesn't prevent it

The Pin to v5 comment is documentation, not enforcement. Dependabot's group bump (github-actions) ignores comments entirely and will keep producing this PR until either (a) the dependency is reverted and added to .github/dependabot.yml ignore rules, or (b) the comment is removed and the bump is accepted intentionally.

How to fix

Two acceptable resolutions:

1. Revert the bump. Restore pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v5.0.0 in all 4 locations and add an ignore for the v6 major in .github/dependabot.yml:

   - dependency-name: "pnpm/action-setup"
     update-types: ["version-update:semver-major"]

2. Accept the bump only after verification. Run the lint job locally / in a test branch with v6.0.3, confirm git diff --exit-code pnpm-lock.yaml still passes, then delete the "Pin to v5" comments in all 4 locations so they don't mislead future maintainers — and ideally hold until pnpm v11 has a stable release rather than tracking v11.0.0-rc.5.

The current PR does neither, leaving the workflow in a state where the inline guidance directly contradicts the pinned version.