[mbret]

Why

Following the setValue deprecation note breaks callers that pass an updater function. The note says to use next, which only sets a value. Signal also keeps two deprecated aliases for what update and the signal itself already do.

• Change: remove both aliases.
• Gain: one name per operation, and no misleading deprecation note.
• Cost: callers still on the aliases migrate (major release).

What's new

• 💥 Signal.setValue and Signal.subject removed

Details

Migration

- signal.setValue((count) => count + 1)
+ signal.update((count) => count + 1)
- signal.subject.pipe(map(format))
+ signal.pipe(map(format))

Hydration

Hydration called setValue, an alias of update. It now calls next. next stores a function value as is, where update would call it as an updater. Stored values are JSON, so a hydrated value is a function only if a custom hydrate returns one.

🔍 Self-reviewed with selfcorrect-review
🤖 Made within harness coverage

---

Generated by Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-03T21:03:20.389940Z	e77cc46	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.