Skip to content

chore(deps): bump @xmtp/node-sdk from 6.0.0-nightly.20260515.1fc0c5c to 6.0.0 (via audit fix) in the xmtp group across 1 directory#40

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/xmtp-b12585372c
Open

chore(deps): bump @xmtp/node-sdk from 6.0.0-nightly.20260515.1fc0c5c to 6.0.0 (via audit fix) in the xmtp group across 1 directory#40
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/xmtp-b12585372c

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 4, 2026

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.


Bumps the xmtp group with 1 update in the / directory: @xmtp/node-sdk.

Updates @xmtp/node-sdk from 6.0.0-nightly.20260515.1fc0c5c to 6.0.0

Release notes

Sourced from @​xmtp/node-sdk's releases.

@​xmtp/node-sdk@​6.0.0

This release includes a performance fix, a breaking change to history sync, and new methods for manual archive management. Update as soon as possible to take advantage of these enhancements and fixes.

Performance improvement

Fixed a performance issue that could cause slowdowns in apps with many conversations or heavy use of disappearing messages.

History sync is now manual

THIS IS A BREAKING CHANGE.

Automatic sending of sync requests on new installations has been removed. XMTP SDKs no longer automatically send sync requests on new clients.

This change gives you explicit control over when sync requests are sent, avoiding unexpected network activity during client initialization.

You must now call sendSyncRequest() explicitly after creating a client on a new installation to trigger a history sync.

To learn more, see Control history sync

Manual history sync archive management

These methods give you fine-grained control over history sync archives. Use them when you need to push data to a new installation proactively, inspect what's available before syncing, or process a specific archive by pin.

  • sendSyncArchive(pin, options?, serverUrl?): Send an archive to the sync group without waiting for a request from another installation

  • listAvailableArchives(daysCutoff): List archives available for import from the sync group

  • processSyncArchive(archivePin?): Process an available archive from the sync group

  • syncAllDeviceSyncGroups(): Sync all device sync groups from the network

To learn more, see Control history sync

Upcoming deprecation of preferences.sync()

In a future release, preferences.sync() will be deprecated. Use syncAllDeviceSyncGroups() instead to sync device sync groups from the network.

To learn more, see Sync device sync groups

Archive-based backups

Support archive-based backups to give your users an easy and durable way to back up their XMTP conversations, messages, and consent preferences from one app installation and import them into another.

This feature includes three core methods:

  • createArchive — Create an encrypted archive
  • archiveMetadata — Read metadata from an archive before importing
  • importArchive — Import an archive into the current installation

To learn more, see Support archive-based backups.

Commits


View in Codesmith
Need help on this PR? Tag @codesmith with what you need.

  • Let Codesmith autofix CI failures and bot reviews

Note

Bump @xmtp/node-sdk from nightly build to stable 6.0.0

Updates @xmtp/node-sdk from the nightly pre-release 6.0.0-nightly.20260515.1fc0c5c to the stable 6.0.0 release. Lockfiles are updated accordingly.

Macroscope summarized b1e74a7.

@macroscopeapp
Copy link
Copy Markdown

macroscopeapp Bot commented May 4, 2026

Approvability

Verdict: Approved

Dependency update from nightly to stable release of @xmtp/node-sdk (6.0.0-nightly → 6.0.0) with security-related dependency overrides. Changes are limited to package.json and lock files with no application code modifications.

You can customize Macroscope's approvability policy. Learn more.

@dependabot dependabot Bot changed the title chore(deps): bump @xmtp/node-sdk from 5.3.0 to 6.0.0 in the xmtp group chore(deps): bump @xmtp/node-sdk from 5.3.0 to 6.0.0 in the xmtp group across 1 directory May 5, 2026
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/xmtp-b12585372c branch 4 times, most recently from 8253a47 to 5fb0713 Compare May 12, 2026 01:06
@dependabot dependabot Bot changed the title chore(deps): bump @xmtp/node-sdk from 5.3.0 to 6.0.0 in the xmtp group across 1 directory chore(deps): bump @xmtp/node-sdk from 6.0.0-nightly.20260515.1fc0c5c to 6.0.0 (via audit fix) in the xmtp group across 1 directory May 15, 2026
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/xmtp-b12585372c branch from 5fb0713 to b8f2506 Compare May 15, 2026 19:35
macroscopeapp[bot]
macroscopeapp Bot previously approved these changes May 15, 2026
Bumps the xmtp group with 1 update in the / directory: [@xmtp/node-sdk](https://github.com/xmtp/xmtp-js/tree/HEAD/packages/node-sdk).


Updates `@xmtp/node-sdk` from 6.0.0-nightly.20260515.1fc0c5c to 6.0.0
- [Release notes](https://github.com/xmtp/xmtp-js/releases)
- [Commits](https://github.com/xmtp/xmtp-js/commits/@xmtp/node-sdk@6.0.0/packages/node-sdk)

---
updated-dependencies:
- dependency-name: "@xmtp/node-sdk"
  dependency-version: 6.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: xmtp
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/xmtp-b12585372c branch from b8f2506 to b1e74a7 Compare May 20, 2026 02:13
@macroscopeapp macroscopeapp Bot dismissed their stale review May 20, 2026 02:13

Dismissing prior approval to re-evaluate b1e74a7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants