Skip to content

changelogs for 1.5.6#3892

Merged
akshaydeo merged 3 commits into
devfrom
05-29-changelogs_for_1.5.6
May 29, 2026
Merged

changelogs for 1.5.6#3892
akshaydeo merged 3 commits into
devfrom
05-29-changelogs_for_1.5.6

Conversation

@akshaydeo

@akshaydeo akshaydeo commented May 29, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR releases core v1.5.14, framework v1.3.14, transports v1.5.6, and bumps all dependent plugins to their respective .14 patch versions. It delivers a broad set of new capabilities across MCP authentication, key rotation, OTel metrics, Bedrock/Anthropic compatibility, and UI improvements, alongside a number of targeted bug fixes and refactors.

Changes

Type of change

  • Bug fix
  • Feature
  • Refactor
  • Documentation
  • Chore/CI

Affected areas

  • Core (Go)
  • Transports (HTTP)
  • Providers/Integrations
  • Plugins
  • UI (React)
  • Docs

How to test

# Core/Transports
go version  # should report go1.26.3
go test ./...

# UI
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build
  • Validate MCP per-user auth by configuring a per-user header auth type and confirming credentials are stored and reconciled on virtual key and MCP client changes.
  • Validate key rotation by triggering a 401/402/403 from an upstream provider and confirming rotation occurs; exhaust all keys and confirm a 502 upstream_credentials_exhausted is returned.
  • Validate OTel metrics output includes provider_cache and semantic_cache attributes.
  • Validate Bedrock requests with tool names exceeding the provider limit are truncated correctly.
  • Validate Opus 4.8 system message handling by sending a request with a system message to an Opus 4.8 endpoint.

Breaking changes

  • Yes
  • No

The deferred-fill user-mode OAuth flow has been removed (#3839). Any integrations relying on that flow must migrate to the new per-user credential store approach. The staticHeadersResolver and serverOAuthResolver identifiers have been renamed to sharedHeadersResolver and sharedOAuthResolver respectively (#3840); any direct references must be updated.

Related issues

#3817, #3656, #3702, #3703, #3704, #3705, #3779, #3783, #3823, #3824, #3825, #3430, #3491, #3865, #3816, #3868, #3878, #3766, #3829, #3810, #3837, #3843, #3739, #3740, #3744, #3745, #3862, #3880, #3838, #3881, #3853, #3855, #3841, #3859, #3849, #3826, #3856, #3840, #3794, #3839, #3782, #3724, #3814, #3836, #3869, #3886

Security considerations

  • MCP per-user credentials are stored via the new MCPCredentialStore abstraction; ensure the backing store is appropriately access-controlled and that credential values are encrypted at rest.
  • The direct API key header feature passes provider secrets via HTTP headers; ensure TLS is enforced on all ingress paths and that headers are not logged in plaintext.
  • User-mode flows are now gated on caller user_id and temp token minting is skipped where appropriate, reducing the surface for privilege escalation.
  • TLS configuration for MCP HTTP/SSE connections supports insecureSkipVerify; this should only be enabled in controlled environments.

Checklist

  • I read docs/contributing/README.md and followed the guidelines
  • I added/updated tests where appropriate
  • I updated documentation where needed
  • I verified builds succeed (Go and UI)
  • I verified the CI pipeline passes locally if applicable

@akshaydeo akshaydeo marked this pull request as ready for review May 29, 2026 15:16
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@coderabbitai

coderabbitai Bot commented May 29, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 06358a1a-2c13-46a1-b4f1-f1a1de9ac9bd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 05-29-changelogs_for_1.5.6

Comment @coderabbitai help to get the list of available commands and usage tips.

akshaydeo commented May 29, 2026

Copy link
Copy Markdown
Contributor Author

@greptile-apps

greptile-apps Bot commented May 29, 2026

Copy link
Copy Markdown
Contributor

Confidence Score: 5/5

This PR touches only changelog and version files; no production code paths are changed.

All 26 changed files are changelog entries and version number increments. There is nothing here that can introduce a runtime regression, data race, or behavior change. The only observations are a format inconsistency in transports/changelog.md and a missing issue reference in two changelog lines, neither of which affects correctness.

No files require special attention — all changes are documentation and version metadata.

Important Files Changed

Filename Overview
transports/changelog.md New changelog with emoji-formatted sections (✨ Features / 🐞 Fixed), different style from all other module changelogs which use plain bullet lists; no code changes.
core/changelog.md New changelog with plain bullet list format; covers all major features and fixes included in core v1.5.14.
framework/changelog.md New changelog with plain bullet list format; covers framework v1.3.14 features and fixes.
plugins/compat/version Bumped from 0.1.12 to 0.1.13, following its own 0.1.x versioning scheme rather than the .14 patch suffix used by other plugins.
core/version Bumped from 1.5.13 to 1.5.14; consistent with PR description.
transports/version Bumped from 1.5.5 to 1.5.6; consistent with PR title and description.
plugins/governance/changelog.md Changelog noting MCP per-user headers auth type support and dependency bump to core v1.5.14/framework v1.3.14.
plugins/telemetry/changelog.md Changelog noting key rotation semantics tightening and provider/semantic cache attributes in metrics export.
plugins/logging/changelog.md Changelog noting dimension rankings logging support and Starlark nested tool call routing refactor.
plugins/otel/changelog.md Changelog noting provider and semantic cache attributes added to metrics export.

Reviews (3): Last reviewed commit: "changelogs for 1.5.6" | Re-trigger Greptile

@akshaydeo akshaydeo force-pushed the 05-29-bedrock_function_toolname_truncation branch from 7880ecb to 7cbfd9b Compare May 29, 2026 15:22
@akshaydeo akshaydeo force-pushed the 05-29-changelogs_for_1.5.6 branch from 4867aaa to 95a6e81 Compare May 29, 2026 15:22
@akshaydeo akshaydeo force-pushed the 05-29-changelogs_for_1.5.6 branch from 95a6e81 to 80f858f Compare May 29, 2026 15:54
@akshaydeo akshaydeo force-pushed the 05-29-bedrock_function_toolname_truncation branch from 7cbfd9b to 9588db5 Compare May 29, 2026 15:54

akshaydeo commented May 29, 2026

Copy link
Copy Markdown
Contributor Author

Merge activity

  • May 29, 4:25 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • May 29, 4:29 PM UTC: @akshaydeo merged this pull request with Graphite.

@akshaydeo akshaydeo changed the base branch from 05-29-bedrock_function_toolname_truncation to graphite-base/3892 May 29, 2026 16:26
@akshaydeo akshaydeo changed the base branch from graphite-base/3892 to dev May 29, 2026 16:28
@akshaydeo akshaydeo merged commit 278b61b into dev May 29, 2026
10 of 11 checks passed
@akshaydeo akshaydeo deleted the 05-29-changelogs_for_1.5.6 branch May 29, 2026 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants