Repository navigation
build(deps): bump actions/setup-node from 4 to 7 - #247
Merged
Merged
Conversation
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 7. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v4...v7) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Deploying specification-website with
|
| Latest commit: |
9c6ecec
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://16d0d7ce.specification-website.pages.dev |
| Branch Preview URL: | https://dependabot-github-actions-ac-w73h.specification-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates actions/setup-node from v4 to v7 in the monthly adoption workflow. The explicit Node 22 selection and npm cache configuration stay the same. The new action also ran successfully in the combined adoption validation; the later Google authentication step was rejected by the identity-provider attribute condition: https://github.com/jdevalk/specification.website/actions/runs/38727259583
Includes the shared lockfile security refresh (
71ef352) used by the other open PRs: sharp, http-cache-semantics, smol-toml and source-map-js, including sharp in the MCP package, within the existing package requirements. Both dependency audits now report zero vulnerabilities.Validation: clean installs, lint, formatting and Agent Skill integrity pass for this branch. The combined result of all nine PRs passes production build, Astro and MCP type-checks, adoption tests and MCP protocol assertions locally; the credential-dependent BigQuery fixture test remains skipped. Fresh GitHub checks were triggered.