Skip to content

fix(deps): update dependency alien-signals-3 to v3.2.1#137

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/alien-signals-3-3.x
Open

fix(deps): update dependency alien-signals-3 to v3.2.1#137
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/alien-signals-3-3.x

Conversation

@renovate

@renovate renovate Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
alien-signals-3 3.1.23.2.1 age confidence

Release Notes

stackblitz/alien-signals (alien-signals-3)

v3.2.1

Compare Source

v3.2.0

Compare Source

Features

  • Effect cleanup functions — Effects can now return a cleanup function that runs before each re-execution and on disposal (#​113)
    effect(() => {
      const handler = () => { /* ... */ };
      document.addEventListener('click', handler);
      return () => document.removeEventListener('click', handler);
    });

Bug Fixes

  • Fix checkDirty resilient to graph mutations during update (#​109, #​110)
  • Fix effectScope not participating in propagation (#​111)
  • Fix inner write blocking future propagation through computed chain (#​112)
  • Fix dispose cleanup running inside tracking context — cleanup reads no longer create spurious dependencies

Note for Custom API Implementors

If you implement custom effect/computed execution using createReactiveSystem, you must wrap the execution body with ++runDepth / --runDepth. This counter drives the innerWrite parameter to propagate, which provides two directions of protection:

  1. Self-protection — the currently-running subscriber (marked RecursedCheck) won't be re-triggered by its own write
  2. Downstream protection — other subscribers are marked Recursed during inner writes, which acts as a bookmark for the propagation state machine. Without this mark, subsequent top-level writes will see stale flags and skip propagation through computed chains — this is the bug fixed in #​112

Testing

Integrate reactive-framework-test-suite — a cross-framework conformance suite with 180 test cases across 13 reactive libraries. alien-signals is the only framework that passes all 180 tests (#​114).

Framework Pass / 180
alien-signals 180
@​preact/signals-core 178
@​vue/reactivity 172
anod 166
tansu 163
@​solidjs/signals 161
solid-js 154
mobx 148
signal-polyfill (TC39) 145
@​angular/core 141
svelte 131
S.js 130
@​reactively/core 114

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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.

@codecov

codecov Bot commented Jun 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.92%. Comparing base (bcfff77) to head (074b18d).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #137   +/-   ##
=======================================
  Coverage   83.92%   83.92%           
=======================================
  Files         137      137           
  Lines        2954     2954           
  Branches      549      549           
=======================================
  Hits         2479     2479           
  Misses        337      337           
  Partials      138      138           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate Bot force-pushed the renovate/alien-signals-3-3.x branch from d2f4d60 to 074b18d Compare June 11, 2026 14:43
@renovate renovate Bot force-pushed the renovate/alien-signals-3-3.x branch from 074b18d to bdc3507 Compare June 19, 2026 11:51
@renovate

renovate Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 61 workspace projects
.                                        | [WARN] There are cyclic workspace dependencies: /tmp/renovate/repos/github/TrigenSoftware/nano_kit/packages/nanoviews, /tmp/renovate/repos/github/TrigenSoftware/nano_kit/packages/storybook
? Verifying lockfile against supply-chain policies (1426 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 35, reused 0, downloaded 0, added 0
Progress: resolved 39, reused 0, downloaded 1, added 0
Progress: resolved 42, reused 0, downloaded 1, added 0
Progress: resolved 46, reused 0, downloaded 1, added 0
Progress: resolved 50, reused 0, downloaded 1, added 0
Progress: resolved 51, reused 0, downloaded 1, added 0
Progress: resolved 52, reused 0, downloaded 1, added 0
Progress: resolved 57, reused 0, downloaded 1, added 0
Progress: resolved 58, reused 0, downloaded 1, added 0
Progress: resolved 59, reused 0, downloaded 1, added 0
Progress: resolved 60, reused 0, downloaded 1, added 0
Progress: resolved 61, reused 0, downloaded 1, added 0
Progress: resolved 62, reused 0, downloaded 1, added 0
[WARN] Request took 11202ms: https://registry.npmjs.org/@tanstack%2Freact-start
Progress: resolved 63, reused 0, downloaded 1, added 0
[WARN] Request took 14507ms: https://registry.npmjs.org/@tanstack%2Freact-router
Progress: resolved 69, reused 0, downloaded 1, added 0
Progress: resolved 74, reused 0, downloaded 1, added 0
Progress: resolved 80, reused 0, downloaded 1, added 0
[WARN] Request took 17730ms: https://registry.npmjs.org/@sveltejs%2Fkit
Progress: resolved 82, reused 0, downloaded 1, added 0
Progress: resolved 84, reused 0, downloaded 1, added 0
Progress: resolved 85, reused 0, downloaded 1, added 0
[WARN] Request took 20105ms: https://registry.npmjs.org/@types%2Fnode
Progress: resolved 86, reused 0, downloaded 1, added 0
[WARN] Request took 22077ms: https://registry.npmjs.org/@storybook%2Fbuilder-vite
Progress: resolved 87, reused 0, downloaded 1, added 0
Progress: resolved 90, reused 0, downloaded 1, added 0
Progress: resolved 91, reused 0, downloaded 1, added 0
Progress: resolved 96, reused 0, downloaded 1, added 0
[WARN] Request took 15455ms: https://registry.npmjs.org/react
[WARN] Request took 15624ms: https://registry.npmjs.org/react-dom
Progress: resolved 97, reused 0, downloaded 1, added 0
[WARN] Request took 17312ms: https://registry.npmjs.org/typescript
[WARN] Request took 20511ms: https://registry.npmjs.org/playwright
✗ Lockfile failed supply-chain policy check (1426 entries in 39.8s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 8 lockfile entries failed verification:
  @typescript/native-preview-darwin-arm64@7.0.0-dev.20260619.1 was published at 2026-06-19T08:00:52.055Z, within the minimumReleaseAge cutoff (2026-06-18T11:51:09.609Z)
  @typescript/native-preview-darwin-x64@7.0.0-dev.20260619.1 was published at 2026-06-19T08:00:47.744Z, within the minimumReleaseAge cutoff (2026-06-18T11:51:09.609Z)
  @typescript/native-preview-linux-arm@7.0.0-dev.20260619.1 was published at 2026-06-19T08:00:39.761Z, within the minimumReleaseAge cutoff (2026-06-18T11:51:09.609Z)
  @typescript/native-preview-linux-arm64@7.0.0-dev.20260619.1 was published at 2026-06-19T08:00:43.928Z, within the minimumReleaseAge cutoff (2026-06-18T11:51:09.609Z)
  @typescript/native-preview-linux-x64@7.0.0-dev.20260619.1 was published at 2026-06-19T08:00:36.005Z, within the minimumReleaseAge cutoff (2026-06-18T11:51:09.609Z)
  @typescript/native-preview-win32-arm64@7.0.0-dev.20260619.1 was published at 2026-06-19T08:00:32.043Z, within the minimumReleaseAge cutoff (2026-06-18T11:51:09.609Z)
  @typescript/native-preview-win32-x64@7.0.0-dev.20260619.1 was published at 2026-06-19T08:00:27.825Z, within the minimumReleaseAge cutoff (2026-06-18T11:51:09.609Z)
  @typescript/native-preview@7.0.0-dev.20260619.1 was published at 2026-06-19T08:00:54.818Z, within the minimumReleaseAge cutoff (2026-06-18T11:51:09.609Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

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