v1.5.0-prerelease5 cut

[akshaydeo]

Summary

Bumps the Go toolchain from 1.26.1 to 1.26.2 across all modules and CI workflows, and cuts new patch/prerelease versions for core, framework, transports, and all plugins to pick up a bug fix in the governance plugin's rate limit persistence.

Changes

• Go version updated to 1.26.2 in all go.mod files, CI workflow steps, and Docker build images (including pinned SHA digests for golang:1.26.2-alpine3.23)
• core bumped to v1.5.4, framework to v1.3.4, transports to v1.5.0-prerelease5
• All plugins (governance, compat, jsonparser, logging, maxim, mocker, otel, prompts, semanticcache, telemetry) bumped to their respective next patch versions
• Governance fix: DumpRateLimits now includes access profile rate limit counters, which were previously always persisted as 0 due to a missing range in the dump logic
• Changelog entries added for the governance fix and dependency upgrades across all affected modules

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

# Verify Go version
go version  # should report go1.26.2

# Run tests across modules
go test ./...

# Verify governance rate limit counters are non-zero after activity
# Start the server, generate some requests under an access profile,
# then inspect the DB to confirm rate limit rows are populated correctly.

Screenshots/Recordings

N/A

Breaking changes

• Yes
• No

Related issues

N/A

Security considerations

No security implications. The Go patch release and Docker image digest update may include upstream security fixes in the Go toolchain itself.

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

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Summary by CodeRabbit

• New Features

  • Added declarative seeding of enterprise Access Profiles from configuration and Helm values.
  • Updated preferred Helm field for pinning provider keys.

• Bug Fixes

  • Fixed rate-limit counters persisting to database and displaying incorrectly.
  • Corrected streaming state handling for fallback requests.
  • Made encryption key configuration properly optional in Helm.
  • Fixed pagination and RBAC loading behavior.

• Chores

  • Updated toolchain and runtime dependencies.
  • Version bumps across core components and plugins.

Walkthrough

Go toolchain upgraded uniformly from 1.26.1 to 1.26.2 across all go.mod files, GitHub Actions workflows, and Docker images. Version bumps applied to core (1.5.4), framework (1.3.4), and plugins; transports updated to prerelease5 with new changelog entries documenting upgrades and fixes.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflows .github/workflows/e2e-tests.yml, .github/workflows/helm-release.yml, .github/workflows/pr-tests.yml, .github/workflows/release-cli.yml, .github/workflows/release-pipeline.yml, .github/workflows/snyk.yml	Updated Go version from 1.26.1 to 1.26.2 across all workflow steps.
Module Go Toolchain Files cli/go.mod, core/go.mod, framework/go.mod, plugins/compat/go.mod, plugins/governance/go.mod, plugins/jsonparser/go.mod, plugins/logging/go.mod, plugins/maxim/go.mod, plugins/mocker/go.mod, plugins/otel/go.mod, plugins/prompts/go.mod, plugins/semanticcache/go.mod, plugins/telemetry/go.mod, .github/workflows/scripts/schemasync/go.mod, transports/go.mod, tests/.../go.mod (7 test modules), examples/mcps/*/go.mod (5 modules), examples/plugins/*/go.mod (5 modules)	Updated Go toolchain directive from 1.26.1 to 1.26.2 across all go.mod files.
Version Files core/version, framework/version, plugins/compat/version, plugins/governance/version, plugins/jsonparser/version, plugins/logging/version, plugins/maxim/version, plugins/mocker/version, plugins/otel/version, plugins/prompts/version, plugins/semanticcache/version, plugins/telemetry/version, transports/version	Version bumps: core 1.5.3→1.5.4, framework 1.3.3→1.3.4, most plugins 1.5.3→1.5.4 (maxim 1.6.3→1.6.4, otel 1.2.3→1.2.4, prompts 1.0.3→1.0.4, compat 0.1.2→0.1.3), transports 1.5.0-prerelease4→1.5.0-prerelease5.
Changelog Files framework/changelog.md, plugins/compat/changelog.md, plugins/governance/changelog.md, plugins/jsonparser/changelog.md, plugins/logging/changelog.md, plugins/maxim/changelog.md, plugins/mocker/changelog.md, plugins/otel/changelog.md, plugins/prompts/changelog.md, plugins/semanticcache/changelog.md, plugins/telemetry/changelog.md, transports/changelog.md	Added changelog entries documenting core/framework version upgrades (and governance plugin rate-limit dump fix). Transports changelog includes new features for declarative enterprise access profile seeding and key_ids Helm preference, plus fixes for stream state, rate-limit persistence, encryption key optionality, and TeamsView pagination.
Docker Base Images transports/Dockerfile, transports/Dockerfile.local	Updated Go builder image from golang:1.26.1-alpine3.23 to golang:1.26.2-alpine3.23 with corresponding digest updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• go upgrade to 1.26.1 #2060 — Predecessor Go version bump from 1.26 to 1.26.1 affecting the same class of files.
• v1.5.0-prerelease4 cut #2877 — Related concurrent modifications to go.mod/version files and CI workflows with comparable scope.

Suggested reviewers

• danpiths
• Pratham-Mishra04

Poem

🐰 From 1.26.1, we hopped to the new,
Go's version two-point-two, shiny and true,
Core, framework, plugins in harmony's beat,
Version bumps across the repo so neat!
Changelog entries sing of our way,
A coordinated upgrade, hip-hip-hooray! 🎉

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The linked issue #123 requests Files API support for providers, but the PR changeset contains only Go version upgrades, version bumps, and a governance rate limit persistence fix. No Files API implementation is present in the changes.	This PR does not address the Files API support requirements from issue #123. Either link the correct issue or implement the requested Files API functionality before merging.
Out of Scope Changes check	⚠️ Warning	The PR includes changes that are out of scope relative to the linked issue #123 (Files API Support). All changes in this PR—Go version bumps, version cuts, and governance rate limit fixes—are unrelated to implementing file upload APIs for providers.	Remove the link to issue #123 or add only the related changes. This PR should focus on the version cut and governance fix, which are separate from the Files API feature work.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title 'v1.5.0-prerelease5 cut' clearly and concisely describes the main change: a release cut for version v1.5.0-prerelease5, which aligns with the changeset's version bumps across all modules.
Description check	✅ Passed	The PR description follows the provided template with all required sections completed: Summary, Changes, Type of change, Affected areas, How to test, Screenshots/Recordings, Breaking changes, Related issues, Security considerations, and Checklist. It provides comprehensive details about the version updates and the governance bug fix.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 04-21-v1.5.0-prerelease5_cut

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Trivy (0.69.3)

Failed to read Trivy output file: ENOENT: no such file or directory, open '/inmem/1269/nsjail-2dc74983-b86f-42f4-ba66-95c518ecc493/merged/.trivy-output.json'

🔧 golangci-lint (2.11.4)

level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies"

---

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

[CLAassistant]

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.}

[akshaydeo]

• v1.5.0-prerelease5 cut #2903 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

🧪 Test Suite Available

This PR can be tested by a repository admin.

Run tests for PR #2903

[greptile-apps]

Confidence Score: 5/5

Safe to merge — purely mechanical release-cut with no logic changes

All changes are version bumps, Go toolchain upgrades (1.26.1 → 1.26.2), Docker image digest updates, and changelog entries. No business logic was modified.

No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/release-pipeline.yml	Go version bumped from 1.26.1 to 1.26.2 across all job steps; no logic changes
transports/Dockerfile	Base image updated to golang:1.26.2-alpine3.23 with updated SHA digest
transports/Dockerfile.local	Base image updated to golang:1.26.2-alpine3.23 with updated SHA digest (mirrors Dockerfile change)
transports/changelog.md	New prerelease5 entries prepended at top with separator; changelog accumulation pattern appears intentional
transports/go.mod	Go directive bumped to 1.26.2
core/go.mod	Go directive bumped to 1.26.2
transports/version	Version bumped from 1.5.0-prerelease4 to 1.5.0-prerelease5
framework/changelog.md	Single-line chore entry noting core upgrade to v1.5.4

_{Reviews (1): Last reviewed commit: "v1.5.0-prerelease5 cut" | Re-trigger Greptile}

[akshaydeo]

Merge activity

• Apr 21, 2:54 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Apr 21, 2:55 PM UTC: @akshaydeo merged this pull request with Graphite.