Skip to content

build(ci): bump actions/setup-node from 4.4.0 to 7.0.0 - #44

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-node-7.0.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-node-7.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 24, 2026

Copy link
Copy Markdown

Bumps actions/setup-node from 4.4.0 to 7.0.0.

Release notes

Sourced from actions/setup-node's releases.

v7.0.0

What's Changed

Enhancements:

Bug fixes:

Documentation updates:

Dependency update:

New Contributors

Full Changelog: actions/setup-node@v6...v7.0.0

v6.5.0

What's Changed

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

v6.4.0

What's Changed

Dependency updates:

New Contributors

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

v6.3.0

What's Changed

Enhancements:

... (truncated)

Commits
  • 8207627 Migrate to ESM and upgrade dependencies (#1574)
  • 04be95c Add cache-primary-key and cache-matched-key as outputs (#1577)
  • 7c2c68d docs: Update caching recommendations to mitigate cache poisoning risks (#1567)
  • 6a61c03 Merge pull request #1569 from jasongin/update-actions-cache-5.1.0
  • 30eb73b Resolve high-severity audit issues
  • 4e1a87a Update dist
  • 360237f Strict equality
  • 4f8aac5 Bump @​actions/cache to 5.1.0, log cache write denied
  • f4a67bb Only use mirrorToken in getManifest if it's provided (#1548)
  • 0355742 Remove dummy NODE_AUTH_TOKEN export (#1558)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4.4.0 to 7.0.0.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@49933ea...8207627)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot @github

dependabot Bot commented on behalf of github Sep 24, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

ethos-pramaan pushed a commit that referenced this pull request Sep 24, 2026
…re stale

The release row said "release commit on local `main`" because that was
true when it was written, an hour before the tag existed. Measured now:
`v0.61.0` = `3bec4fa`, `release-artifacts.yml` run 36033240012 green in
28m 8s — four targets, every one `verified`, and the assembly step's own
words are `one fingerprint on all 4 runners`, which is the condition
under which `SHA256SUMS.txt` gets written at all. CI #112 green on the
same commit.

The security row was overtaken by events on the day it was written. It
said secret scanning, push protection and org-wide 2FA "cannot be
changed from here" and were all off. Two of the three were turned on
the same day from the browser, on the owner's explicit grant, and the
`v0.61.0` push has now gone through push protection without a hit.
Org-wide 2FA stays off deliberately — enforcing it can lock out org
members who have not enrolled, which is the owner's to schedule, not a
thing to switch on while cutting a release. Private vulnerability
reporting is the one remaining switch with no side effect.

`dependabot.yml`, added this cycle in `6e97637`, has run: ten version
PRs, #35-#44. Two are recorded by name because they are not routine —
#43 bumps `lopdf`, whose version is a PROFILE FIELD (`backend.version`),
so merging it moves `profile_sha256` and is a reader change requiring
its own measurement; #40 jumps `skrifa` eight minors across the font
metrics `advance-over-font-envelope-v1` is built on. Neither is an
auto-merge, and saying so here is cheaper than finding out in a gate.

No code changed. Every number is read from the run or the settings page,
not inferred from a green tick.

Signed-off-by: docushell-dev <[email protected]>
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.

0 participants