Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 4, 2025

📦 Release Preparation

0.37.0 (2026-02-03)

⚠ BREAKING CHANGES

  • transition from ethers to viem (#555)
  • 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)
  • add devnet support (#527) (773551b)
  • change to only export Synapse from the main entrypoint (4c0cc47), closes #232
  • Endorsements Service (#553) (fba3280)
  • examples/cli: add get-sp-peer-ids command (#546) (8aafdf1)
  • move ethers to peer dependencies (242a2c1)
  • storage: rename "pieces" callbacks, add piece info & dataSetId (#439) (f1bd585)
  • transition from ethers to viem (#555) (3741241)
  • 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
  • remove telemetry (#562) (128037e)
  • 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


🚀 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
Copy link

cloudflare-workers-and-pages bot commented Dec 4, 2025

Deploying with  Cloudflare Workers  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 0fcbbbb Commit Preview URL

Branch Preview URL
Feb 03 2026, 03:59 PM

@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch 9 times, most recently from 965c603 to a9559df Compare December 10, 2025 19:14
@socket-security
Copy link

socket-security bot commented Dec 10, 2025

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch 3 times, most recently from efd0e10 to d3932e5 Compare December 11, 2025 18:15
@github-actions github-actions bot changed the title chore(master): release synapse-sdk 0.36.2 chore(master): release synapse-sdk 0.37.0 Dec 12, 2025
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch 2 times, most recently from b30a6c1 to 186daf4 Compare December 15, 2025 12:27
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch 3 times, most recently from 0f9afba to b05b001 Compare December 16, 2025 15:05
@BigLep
Copy link
Contributor

BigLep commented Dec 17, 2025

@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 BigLep moved this from 📌 Triage to 🐱 Todo in FOC Dec 17, 2025
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch 2 times, most recently from c6b0f8b to 0bf6bf3 Compare December 18, 2025 11:13
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch 2 times, most recently from 4359249 to 5713006 Compare January 5, 2026 16:45
@BigLep
Copy link
Contributor

BigLep commented Jan 5, 2026

@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?

@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch 6 times, most recently from 6a14ff2 to dd9610e Compare January 12, 2026 03:59
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch 2 times, most recently from 84fbb10 to 4aadc15 Compare January 15, 2026 01:52
@BigLep BigLep added this to the M4: Filecoin Service Liftoff milestone Jan 15, 2026
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch from 4aadc15 to 0c74ed5 Compare January 15, 2026 11:05
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch from 0c74ed5 to 9c78263 Compare January 19, 2026 05:27
@rjan90 rjan90 mentioned this pull request Jan 19, 2026
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch 6 times, most recently from 86f3e4d to 9179b3f Compare January 26, 2026 13:24
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch from 9179b3f to d73b4eb Compare January 27, 2026 02:45
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-sdk branch from d73b4eb to 0fcbbbb Compare February 3, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: 🐱 Todo

Development

Successfully merging this pull request may close these issues.

Add type validation to docs settleRail no-longer requires a FIL fee transfer Stop exporting all the things on the top level

2 participants