chore: release master

[weboko]

🤖 I have created a release beep boop

core: 0.0.41

0.0.41 (2025-11-21)

Features

• Reliable Channel: Status Sync, overflow protection, stop TODOs (#2729) (e5f51d7)

Bug Fixes

• Cleanup routines on reliable channel and core protocols (#2733) (84a6ea6)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/enr bumped from ^0.0.33 to ^0.0.34
    • @waku/interfaces bumped from 0.0.34 to 0.0.35
    • @waku/utils bumped from 0.0.27 to 0.0.28

discovery: 0.0.14

0.0.14 (2025-11-21)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/core bumped from 0.0.40 to 0.0.41
    • @waku/enr bumped from 0.0.33 to 0.0.34
    • @waku/interfaces bumped from 0.0.34 to 0.0.35
    • @waku/utils bumped from 0.0.27 to 0.0.28

enr: 0.0.34

0.0.34 (2025-11-21)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/utils bumped from 0.0.27 to 0.0.28
  • devDependencies
    • @waku/interfaces bumped from 0.0.34 to 0.0.35

interfaces: 0.0.35

0.0.35 (2025-11-21)

Bug Fixes

• Cleanup routines on reliable channel and core protocols (#2733) (84a6ea6)

message-encryption: 0.0.39

0.0.39 (2025-11-21)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/core bumped from 0.0.40 to 0.0.41
    • @waku/interfaces bumped from 0.0.34 to 0.0.35
    • @waku/utils bumped from 0.0.27 to 0.0.28

react: 0.0.9

0.0.9 (2025-11-21)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/interfaces bumped from 0.0.34 to 0.0.35
    • @waku/sdk bumped from 0.0.36 to 0.0.37
    • @waku/utils bumped from 0.0.27 to 0.0.28

relay: 0.0.24

0.0.24 (2025-11-21)

Bug Fixes

• Cleanup routines on reliable channel and core protocols (#2733) (84a6ea6)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/core bumped from 0.0.40 to 0.0.41
    • @waku/sdk bumped from 0.0.36 to 0.0.37
    • @waku/interfaces bumped from 0.0.34 to 0.0.35
    • @waku/utils bumped from 0.0.27 to 0.0.28

rln: 0.1.11

0.1.11 (2025-11-21)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/core bumped from ^0.0.40 to ^0.0.41
    • @waku/utils bumped from ^0.0.27 to ^0.0.28
  • devDependencies
    • @waku/interfaces bumped from 0.0.34 to 0.0.35
    • @waku/message-encryption bumped from ^0.0.38 to ^0.0.39

run: 0.0.3

0.0.3 (2025-11-21)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/core bumped from 0.0.40 to 0.0.41
    • @waku/interfaces bumped from * to 0.0.35
    • @waku/sdk bumped from 0.0.36 to 0.0.37
    • @waku/utils bumped from * to 0.0.28

sdk: 0.0.37

0.0.37 (2025-11-21)

Features

• Incorporate sds-r into reliable channels (#2701) (788f7e6)
• Reliable Channel: Status Sync, overflow protection, stop TODOs (#2729) (e5f51d7)

Bug Fixes

• Cleanup routines on reliable channel and core protocols (#2733) (84a6ea6)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/core bumped from 0.0.40 to 0.0.41
    • @waku/discovery bumped from 0.0.13 to 0.0.14
    • @waku/interfaces bumped from 0.0.34 to 0.0.35
    • @waku/sds bumped from ^0.0.8 to ^0.0.9
    • @waku/utils bumped from 0.0.27 to 0.0.28
  • devDependencies
    • @waku/message-encryption bumped from ^0.0.38 to ^0.0.39

sds: 0.0.9

0.0.9 (2025-11-21)

Features

• Incorporate sds-r into reliable channels (#2701) (788f7e6)
• Reliable Channel: Status Sync, overflow protection, stop TODOs (#2729) (e5f51d7)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/utils bumped from ^0.0.27 to ^0.0.28

utils: 0.0.28

0.0.28 (2025-11-21)

Features

• Reliable Channel: Status Sync, overflow protection, stop TODOs (#2729) (e5f51d7)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @waku/interfaces bumped from 0.0.34 to 0.0.35

---

This PR was generated with Release Please. See documentation.

[github-actions]

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
Waku node	96.24 KB (0%)	2 s (0%)	1.5 s (+53.08% 🔺)	3.5 s
Waku Simple Light Node	147.6 KB (0%)	3 s (0%)	1.2 s (-9.44% 🔽)	4.1 s
ECIES encryption	22.62 KB (0%)	453 ms (0%)	503 ms (-7.24% 🔽)	955 ms
Symmetric encryption	22 KB (0%)	440 ms (0%)	376 ms (-7.7% 🔽)	816 ms
DNS discovery	52.17 KB (0%)	1.1 s (0%)	701 ms (-11.45% 🔽)	1.8 s
Peer Exchange discovery	52.91 KB (0%)	1.1 s (0%)	586 ms (+20.4% 🔺)	1.7 s
Peer Cache Discovery	46.64 KB (0%)	933 ms (0%)	754 ms (+55.79% 🔺)	1.7 s
Privacy preserving protocols	77.31 KB (0%)	1.6 s (0%)	1.1 s (-10.66% 🔽)	2.6 s
Waku Filter	79.82 KB (0%)	1.6 s (0%)	970 ms (-9.38% 🔽)	2.6 s
Waku LightPush	77.97 KB (0%)	1.6 s (0%)	950 ms (-11.71% 🔽)	2.6 s
History retrieval protocols	83.74 KB (0%)	1.7 s (0%)	776 ms (-18.77% 🔽)	2.5 s
Deterministic Message Hashing	28.98 KB (0%)	580 ms (0%)	414 ms (-26.01% 🔽)	994 ms

[chatgpt-codex-connector]

💡 Codex Review

https://github.com/waku-org/js-waku/blob/5112516ee02d95f318bd424bc8950eb7227ca12e/packages/browser-tests/package.json#L19-L25
Keep browser tests aligned with utils 0.0.28

This release bumps @waku/utils to 0.0.28 everywhere else, but packages/browser-tests/package.json still pins @waku/utils to "0.0.27". Because the dependency is an exact version, npm workspaces will no longer consider the local @waku/[email protected] as satisfying this requirement and will instead try to download 0.0.27 from the registry (or fail completely when offline). As a result, the Playwright browser tests now exercise an older published build rather than the code being released, so regressions in utils can slip through and workspace installs can break. Please bump this dependency (and the lockfile entry) to 0.0.28 so the tests keep running against the current workspace package.

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".