Skip to content

chore(deps): update dependency @effect/platform-node to v4.0.6 - #534

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/effect-platform-node-4.x
Closed

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/effect-platform-node-4.x

Conversation

@renovate

@renovate renovate Bot commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@effect/platform-node (source) 4.0.5 → 4.0.6 age confidence

Release Notes

Effect-TS/effect (@​effect/platform-node)

v4.0.6

Compare Source

Patch Changes

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot enabled auto-merge (squash) October 29, 2026 22:48
@GraemeF

GraemeF commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

Held. This moves @effect/platform-node to 4.0.6 alone, while effect and @effect/platform-node-shared stay at 4.0.5. platform-node 4.0.6 declares effect ^4.0.6 as a peer, so it cannot land on its own, and CI is red because pluginModules' fixed-output hash in flake.nix did not move. #531 and #533 are held for the same reason. All three move together in one change, the way #461 did for 4.0.5. Once that lands, this is closed with a link to it.

GraemeF added a commit that referenced this pull request Oct 30, 2026
…535)

@effect/platform-node 4.0.6 and @effect/platform-node-shared 4.0.6
declare effect ^4.0.6 as a peer, so Renovate's three separate bumps
(#531, #533, #534) cannot land one at a time. This moves all three pins,
the plugin lock and pluginModules' hash in one change.

The lock moves only the three effect packages, and the undici it already
holds meets platform-node's new range. The 4.0.6 notes are fixes and
additions. FileSystem.lstat is new, and a custom FileSystem must now
provide it, but the plugin uses only NodeFileSystem. EPERM now reads as
PermissionDenied rather than Unknown, and the plugin matches on neither.
Imports of effect's nested internal modules are now blocked, and the
plugin imports only public entry points. The rest touches HTTP servers,
clusters, event logs and the CLI, none of which the plugin uses.
@GraemeF

GraemeF commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

Superseded by #535, which moved effect, @effect/platform-node and @effect/platform-node-shared to 4.0.6 together, with the plugin lock and pluginModules' hash. It merged as fbc60cd with CI green on main.

@GraemeF GraemeF closed this Oct 30, 2026
auto-merge was automatically disabled October 30, 2026 00:55

Pull request was closed

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.

1 participant