Skip to content

Bump @preact/signals from 2.9.1 to 2.9.2 - #3

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/preact/signals-2.9.2
Closed

Bump @preact/signals from 2.9.1 to 2.9.2#3
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/preact/signals-2.9.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 21, 2026

Copy link
Copy Markdown

Bumps @preact/signals from 2.9.1 to 2.9.2.

Release notes

Sourced from @​preact/signals's releases.

@​preact/signals@​2.9.2

Patch Changes

  • #942 e76780c Thanks @​JoviDeCroock! - Fix stale <For> render-prop indexes after removals/reorders by making each cached item's index reactive (a per-item signal) instead of a frozen prop. Cached children are reused and re-render with the new index rather than being recreated, so DOM/component identity is preserved.

  • #938 e0ce9fd Thanks @​JoviDeCroock! - Fix Signal-bound DOM props getting stranded at a stale value when Preact reuses a DOM node. The prop-binding effect now writes the applied value back into the rendered props, keeping Preact's diff baseline in sync with the DOM instead of assuming Preact applied every update.

  • Updated dependencies [beb84c1]:

    • @​preact/signals-core@​1.14.3
Changelog

Sourced from @​preact/signals's changelog.

2.9.2

Patch Changes

  • #942 e76780c Thanks @​JoviDeCroock! - Fix stale <For> render-prop indexes after removals/reorders by making each cached item's index reactive (a per-item signal) instead of a frozen prop. Cached children are reused and re-render with the new index rather than being recreated, so DOM/component identity is preserved.

  • #938 e0ce9fd Thanks @​JoviDeCroock! - Fix Signal-bound DOM props getting stranded at a stale value when Preact reuses a DOM node. The prop-binding effect now writes the applied value back into the rendered props, keeping Preact's diff baseline in sync with the DOM instead of assuming Preact applied every update.

  • Updated dependencies [beb84c1]:

    • @​preact/signals-core@​1.14.3
Commits

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 [@preact/signals](https://github.com/preactjs/signals/tree/HEAD/packages/preact) from 2.9.1 to 2.9.2.
- [Release notes](https://github.com/preactjs/signals/releases)
- [Changelog](https://github.com/preactjs/signals/blob/main/packages/preact/CHANGELOG.md)
- [Commits](https://github.com/preactjs/signals/commits/@preact/signals@2.9.2/packages/preact)

---
updated-dependencies:
- dependency-name: "@preact/signals"
  dependency-version: 2.9.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 21, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jun 22, 2026

Copy link
Copy Markdown
Author

Looks like @preact/signals is up-to-date now, so this is no longer needed.

@dependabot dependabot Bot closed this Jun 22, 2026
@dependabot
dependabot Bot deleted the dependabot/bun/preact/signals-2.9.2 branch June 22, 2026 10:28
SShadowS added a commit that referenced this pull request Aug 1, 2026
…deferred items

Nine contained fixes from the final whole-branch review of the Stats & Config tab:

- I-4 (most serious): model contamination reported an all-clear over OBSERVED pins
  only. buildAgentModelRows() only ever walked entries, so a declared pin that never
  dispatched (12 of 19 declared frontmatter pins + ci-waiter, live 30d) was silently
  absent rather than counted. Added a 'not-observed' row status, excluded from every
  contamination count (same as 'unpinned') but explicitly disclosed by both consumers
  (stats-integrity.tsx's Contamination section, stats-ribbon.tsx's Model integrity card).
- I-5: tool mix's "none at zero calls" read as coverage this table does not have — a
  never-called tool is ABSENT from tool_calls, not present at zero, so it can never be
  listed. Reworded to state the observed count and name the blind spot; kept the
  currently-unreachable zero-count branch with a comment explaining why, rather than
  deleting defensive code that stays testable via fixtures.
- I-1: cost-per-read-band-item rendered a bare n=76 with no coverage disclosure, while
  the read-band gauge over the identical population discloses Coverage + a caveat
  headline. Reused computeReadBandCoverage/describeReadBandCoverage/
  buildReadBandLowCoverageHeadline verbatim.
- I-2: cross-referenced the Cost card's "Cost by model" table to the Integrity panel's
  identical aggregateModelUsage table, so the page doesn't assert the same [1m] finding
  as two independent measurements.
- I-3: disclosed that the Cost card's per-repo "Reviews" column (cost_usd IS NOT NULL)
  can legitimately disagree with the Operational panel's per-repo "Reviews" (unfiltered)
  — the Operational panel already discloses this; this is the other half.
- Deferred #1: aligned postgres.ts's image_sha ALTER comment with the correct one on
  IPRReviewStore.imageSha (compose bakes "unknown", not null).
- Deferred #3: gave belowBandCount a code comment stating the per-review-vs-per-finding
  distinction the UI already warns readers about.
- Deferred #8 + M-1: removed the duplicate low-sample warning in ReadBandGauge (the
  panel-wide banner already covers it) and made .operational-panel__low-sample match
  the other three panels' quiet italic treatment instead of a warning-tinted box — a
  sample-size caveat is not a warning state.
- Deferred #10: corrected a comment claiming duration/turns are populated on every
  completed review; measured coverage is 99.1%/97.2% (30d/90d), not literally 100%.

+11 tests (model-contamination, stats-integrity, stats-ribbon, stats-operational).
Fixing I-4's tests surfaced a real bug in two pre-existing tests that assumed a
single-row result from a fixture `pins` map that (correctly, after this fix) now also
yields a not-observed row for its other declared pin — updated to look up the row under
test by agent name rather than by position/whole-array equality.

2090 pass / 0 fail (baseline 2079 + 11 new), typecheck clean, dashboard:build clean.

Claude-Session: https://claude.ai/code/session_01Ad8Q2RniB9y2dSbcCKDUad
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 javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants