chore: version packages

[gram-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

cli@0.15.6

Patch Changes

• cfd28c6: Removed the automatic opening of the deployment logs URL in the user's browser when a deployment completes. The URL for logs and deployments is printed to the console and the user can choose to open it if needed.

dashboard@0.32.1

Patch Changes

• 1765931: Removes the logs enabled flag in the telemetry API responses.
• 1500853: Surface correct http status attribute references in MCP logs search
• e616da7: Add admin-only cache purging functionality
• Updated dependencies [1765931]
• Updated dependencies [e616da7]
  • @gram/client@0.27.20

@gram/client@0.27.20

Patch Changes

• 1765931: Removes the logs enabled flag in the telemetry API responses.
• e616da7: Add admin-only cache purging functionality

server@0.27.1

Patch Changes

• 1765931: Removes the logs enabled flag in the telemetry API responses.
• e616da7: Add admin-only cache purging functionality

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
gram-docs-redirect	Ready	Preview, Comment	Mar 9, 2026 11:42pm

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🔴 @gram/client version 0.27.20 is lower than existing CHANGELOG entries (0.27.24, 0.28.0, 0.28.1)

The new @gram/client version 0.27.20 is inserted at the top of the CHANGELOG (client/sdk/CHANGELOG.md:3), but the CHANGELOG already contains entries for higher versions: 0.27.24 (line 10), 0.28.0 (line 16), and 0.28.1 (line 38). This creates a non-monotonic version ordering where the "latest" entry is numerically lower than previous entries. The package.json version is also set to 0.27.20 (client/sdk/package.json:3), which is a version regression from the 0.27.24/0.28.x versions that already appear in the changelog. The dashboard CHANGELOG at client/dashboard/CHANGELOG.md:12 also references @gram/client@0.27.20 as a dependency of dashboard@0.32.1, while the previous dashboard@0.32.0 entry at line 28 already referenced the higher @gram/client@0.27.24. This suggests the release branch diverged before those higher versions were published, and the changeset automation produced an incorrect version bump.

Prompt for agents

The @gram/client package version needs to be corrected. The CHANGELOG at client/sdk/CHANGELOG.md has version 0.27.20 inserted above 0.27.24, and the package.json at client/sdk/package.json sets version to 0.27.20. Since versions 0.27.24, 0.28.0, and 0.28.1 already exist in the changelog (and were presumably published), the new version should be higher than all existing versions. Update client/sdk/package.json version and the new CHANGELOG entry header to use a version higher than 0.28.1 (e.g., 0.28.2). Also update the dependency reference in client/dashboard/CHANGELOG.md line 12 from @gram/client@0.27.20 to the corrected version.

---

Was this helpful? React with 👍 or 👎 to provide feedback.