Skip to content

chore(actions): Bump actions/setup-node from 4 to 6 - #3

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

chore(actions): Bump actions/setup-node from 4 to 6#3
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-node-6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Apr 17, 2026

Copy link
Copy Markdown

Bumps actions/setup-node from 4 to 6.

Release notes

Sourced from actions/setup-node's releases.

v6.0.0

What's Changed

Breaking Changes

Dependency Upgrades

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

v5.0.0

What's Changed

Breaking Changes

This update, introduces automatic caching when a valid packageManager field is present in your package.json. This aims to improve workflow performance and make dependency management more seamless. To disable this automatic caching, set package-manager-cache: false

steps:
- uses: actions/checkout@v5
- uses: actions/setup-node@v5
  with:
    package-manager-cache: false

Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes

Dependency Upgrades

New Contributors

Full Changelog: actions/setup-node@v4...v5.0.0

v4.4.0

... (truncated)

Commits

Dependabot compatibility score

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v4...v6)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Apr 17, 2026
jamesyong-42 added a commit that referenced this pull request Apr 17, 2026
remove() was reading its vis/size contribution from the descendant
cache slot, which holds the subtree TOTAL (self + all descendants).
Subtracting the total from ancestors while leaving children's cache
entries intact made ancestor summaries silently wrong under repeated
remove-dir-without-remove-children sequences. Fix: compute self
contribution directly from the Entry being removed (+1 if visible,
+entry.size). Children's cache entries, if any, are unchanged and
remain reachable for later individual removal. saturating_sub was
masking the drift.

rename() was updating path_to_id only; Entry.name stayed stale. Now
rename clones the Entry, updates its name, reinserts the Arc, and
re-sorts the affected parent's children slot (since sibling order is
by name). Directory rename still returns EUNSUPPORTED until Phase 2's
deferred walker-driven recursive rename lands. path_to_id update now
happens AFTER snapshot publish, matching insert()'s ordering.

Audit findings: Critical #1, Critical #3.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
jamesyong-42 added a commit that referenced this pull request Apr 18, 2026
Previously every lock site in watcher.rs used .expect("mutex poisoned")
so a panic anywhere while holding a lock (user callback panic, notify
internals, allocation failure) turned the entire Watcher into a panic
landmine — every subsequent watch / unwatch / watched_roots call crashed
the caller instead of returning the Result<_, FxError> that the public
API advertises.

Fix: add a lock_recover helper that catches PoisonError and recovers
via into_inner(). The protected data (Vec<PathBuf> of roots, Option<>
handle slots) is safe to observe after a partial write — worst case
is a stale roots list, not memory corruption. Applied at every lock
site, including Drop.

Audit finding: Phase 3/4 review #3 (Critical).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@dependabot @github

dependabot Bot commented on behalf of github Jul 25, 2026

Copy link
Copy Markdown
Author

Superseded by #20.

@dependabot dependabot Bot closed this Jul 25, 2026
@dependabot
dependabot Bot deleted the dependabot/github_actions/actions/setup-node-6 branch July 25, 2026 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants