chore(master): release synapse-sdk 0.37.0

[github-actions]

📦 Release Preparation

0.37.0 (2026-01-08)

⚠ BREAKING CHANGES

• replace getMaxProvingPeriod() and getChallengeWindow() with getPDPConfig() (#526)
• use activePieceCount for accurate piece tracking (#517)
• change to only export Synapse from the main entrypoint

refactor

• replace getMaxProvingPeriod() and getChallengeWindow() with getPDPConfig() (#526) (a4956c7)

Features

• Add API for querying remaining egress (#430) (c40d6b8)
• change to only export Synapse from the main entrypoint (4c0cc47), closes #232
• move ethers to peer dependencies (242a2c1)
• storage: rename "pieces" callbacks, add piece info & dataSetId (#439) (f1bd585)
• use activePieceCount for accurate piece tracking (#517) (59fd863)

Bug Fixes

• cache clientDataSetId in StorageContext (#489) (ec1345a)
• change FilBeam URL to stats.filbeam.com (#539) (87ac7a8)
• createStorageContext without getClientDataSetsWithDetails (#438) (76e2439)
• expose getScheduledRemovals on storageContext (#490) (6a3b5cc)
• remove settlement fee (#502) (8c7537e), closes #243
• resolveByProviderId doesnt use getClientDataSetsWithDetails (1049c05)
• treat status code 202 for findPiece as a retry (6b9e03f)
• warm-storage: check metadata withCDN key in addition to cdnRailId for CDN status (#505) (db234e5)

Chores

• add docs build to packages ci (810d7a8), closes #468
• fix test that randomly fails (9752c76)
• pnpm security and catalog (123b89c)
• remove only from tests (3d6293b)
• rename signerAddress to clientAddress (#488) (552d6fd)
• update msw (#465) (ea02a6d)
• update ox and ensure pnpm version (#510) (caef545)
• update viem/wagmi and markdown lint (#478) (3f023f6)
• use json rpc mocks from core (a7b3913)

---

🚀 How to Release

1. Review the changelog and version bump in this PR
2. Merge this PR to trigger the release
3. After merging, the workflow will:
   • Create a GitHub release with tag ${version}
   • Publish to npm automatically
4. Wait until the workflow is complete before merging another release PR

⚠️ Note: The release has NOT been created yet. It will only be created after you merge this PR.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	synapse-dev	6a14ff2	Commit Preview URL Branch Preview URL	Jan 08 2026, 12:44 PM

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: ? → npm/mermaid@11.12.2 → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm vite is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/vite-tsconfig-paths@6.0.3 → npm/@hugomrdias/docs@0.1.11 → npm/astro@5.16.7 → npm/vite@6.4.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/vite@6.4.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[BigLep]

@hugomrdias : do you think we'll do a release in December, or wait for January? Feel free to put it in the corresponding cycle.

[BigLep]

@hugomrdias : looks like more need to get a Synapse release out per https://filecoinproject.slack.com/archives/C08TVNKJV7C/p1767631790416129 . Any reason for us not to do a release?

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	starlight-auto-sidebar@​0.1.4
	starlight-changelogs@​0.2.3
	starlight-links-validator@​0.19.2
	typedoc-plugin-missing-exports@​4.1.2
	rehype-external-links@​3.0.0
	typedoc-plugin-mdn-links@​5.0.10
	vite-tsconfig-paths@​6.0.3
	sharp@​0.34.5
	typedoc@​0.28.15
	wrangler@​4.58.0

View full report