chore(main): release 0.56.0

[sdp-release-bot]

Release 0.56.0

This pull request was generated by the release workflow.

Auto-merge is enabled. After review approval and required checks pass, GitHub will squash-merge this PR and the release workflow will publish the tag and GitHub release.

Required repository settings: Allow auto-merge and Allow squash merging.

0.56.0 (2026-08-07)

Features

• private-channels: resolve event ids to display names (#1140) (12a7a5a)
• web: give every token holding a page to open (#1091) (e9bd859)
• web: end onboarding by showing what setup created (#1123) (d97b1c3)

Bug Fixes

• security: make audit ledger tamper-evident (#1090) (9dc59bd)
• web: stop the filter count appearing twice on the transactions toolbar (#1097) (397cae7)
• policy: execute approved wallet operations (#1096) (781e229)
• web: show token symbols in the transactions asset filter (#1114) (5436c58)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
sdp-docs	Ready	Preview	Aug 7, 2026 6:53am
sdp-web (dev)	Ready	Preview	Aug 7, 2026 6:53am

[greptile-apps]

Greptile Summary

The PR prepares release 0.56.0, but its sole commit is unsigned despite the repository's mandatory verified-commit policy.

• Bumps the root package and release manifest from 0.55.0 to 0.56.0.
• Adds the generated 0.56.0 changelog section.
• Requires the release commit to be recreated with a verifiable signature before merge.

Confidence Score: 4/5

This PR should not merge until its unsigned release commit is replaced with a signed, verified commit.

The release metadata is internally consistent, but the only commit in the pull request has no cryptographic signature and violates the repository's mandatory commit-verification policy.

Files Needing Attention: package.json, CHANGELOG.md, and .github/.release-please-manifest.json

Important Files Changed

Filename	Overview
.github/.release-please-manifest.json	Updates the release manifest to 0.56.0 consistently with the other release metadata.
CHANGELOG.md	Adds the generated 0.56.0 release notes and the expected v0.55.0-to-v0.56.0 comparison link.
package.json	Correctly updates the root version to 0.56.0, but the containing release commit is unsigned and therefore violates the verified-commit requirement.

_{Reviews (1): Last reviewed commit: "chore(main): release 0.56.0" | Re-trigger Greptile}

[greptile-apps]

Unsigned release commit

The sole commit in this pull request has no cryptographic signature, so merging this release would violate the repository's mandatory signed-and-verified commit policy. Recreate the release commit with a verifiable signature before merging.

Context Used: Request changes if the commits are not signed (ver... (source)