Skip to content

1.5.7 changelogs - #4117

Closed
akshaydeo wants to merge 1 commit into
devfrom
05-30-1.5.7_changelogs
Closed

1.5.7 changelogs#4117
akshaydeo wants to merge 1 commit into
devfrom
05-30-1.5.7_changelogs

Conversation

@akshaydeo

@akshaydeo akshaydeo commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Changes

  • Resolved merge conflicts in core/changelog.md, core/version, framework/changelog.md, framework/version, and all plugin changelog/version files, keeping the HEAD versions (1.5.17 / 1.3.17 / plugin patch .17 series)
  • Resolved conflict in transports/changelog.md and transports/version, retaining the 1.5.9 transport release notes and discarding the older 1.5.7 backport content
  • The 1.5.7-era entries being dropped from HEAD were: Ollama and SGL streaming Authorization header fixes (ollama streaming auth header #3906, fix: SGL provider - send Authorization header on streaming requests #3307), the from_memory query parameter removal (removes from_memory for APIs #3903), and the associated CVE remediation detail block — all of which are already captured in earlier releases

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 no conflict markers remain in any changelog or version file
grep -r "<<<<<<\|=======\|>>>>>>>" core/ framework/ plugins/ transports/

# Confirm version files contain only the expected version strings
cat core/version          # expect: 1.5.17
cat framework/version     # expect: 1.3.17
cat transports/version    # expect: 1.5.9

Breaking changes

  • No

Related issues

  • Backport branch: 87aec5828 (1.5.7 changelogs)

Security considerations

No functional code changes. Changelog and version metadata only.

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

Summary by CodeRabbit

  • New Features

    • Added wildcard support for request headers pattern capture.
    • Added support for multiple OpenTelemetry collectors.
  • Bug Fixes

    • Fixed chat parameter token preservation during filtering.
    • Fixed passthrough budgets handling.
  • Chores

    • Updated core to v1.5.17.
    • Updated framework to v1.3.17.
    • Resolved dependency security vulnerabilities.

@coderabbitai

coderabbitai Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This PR updates the project version to 1.5.17 and synchronizes changelog entries across core, framework, transports, and all plugins. Changes include repositioning changelog items, adding new entries for recent fixes and features, and updating dependency version references in plugin changelogs.

Changes

Release version and changelog synchronization

Layer / File(s) Summary
Core version bump and changelog
core/version, core/changelog.md
Core version is set to 1.5.17. The golang.org/x dependencies security remediation changelog entry (#3900) is positioned in the core changelog.
Framework and transports changelog updates
framework/changelog.md, transports/changelog.md
Framework changelog repositions the governance_virtual_keys column removal entry (#3670). Transports changelog reorganizes sections to prioritize security.
Plugin changelog and dependency synchronization
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
All plugin changelogs are updated to reflect new feature and fix entries (e.g., chat max_tokens preservation, passthrough budgets, request_headers with wildcard support, multiple OTel collectors) and synchronized with core v1.5.17 and framework v1.3.17 dependency versions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • maximhq/bifrost#4096: Both PRs are coordinated release updates touching the same version and changelog artifacts as part of the larger v1.5.17 release cycle.

Suggested reviewers

  • danpiths
  • Pratham-Mishra04

Poem

📝✨ A changelog dance across the land,
Version bumps now perfectly planned,
From core to plugins, far and wide,
1.5.17 with features as our guide,
Release prep hopping by a rabbit's hand! 🐇

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Linked Issues check ⚠️ Warning The linked issue #123 is about Files API support for providers, while this PR addresses changelog/version merge conflicts unrelated to that objective. Review the linked issues; this PR does not implement Files API support. Either remove the incorrect issue link or add changes that address #123 requirements.
Title check ❓ Inconclusive The title '1.5.7 changelogs' is partially related to the changeset; it mentions versioning but does not reflect the actual content showing version 1.5.17, 1.3.17, and 1.5.9 updates across multiple changelog files. Update the title to accurately reflect the actual version numbers being updated (e.g., '1.5.17/1.3.17 changelogs and version bump' or similar) for clarity.
✅ Passed checks (3 passed)
Check name Status Explanation
Description check ✅ Passed The PR description provides clear details about merge conflict resolution and version updates, but is missing required template sections including testing confirmation, screenshots, and a complete checklist.
Out of Scope Changes check ✅ Passed The PR contains only changelog and version file updates consistent with resolving merge conflicts, with no code changes outside this scope.
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 05-30-1.5.7_changelogs

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

@CLAassistant

CLAassistant commented Jun 7, 2026

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.

Copy link
Copy Markdown
Contributor Author

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

@akshaydeo
akshaydeo force-pushed the 05-30-1.5.7_changelogs branch from 87aec58 to 20e54cb Compare June 7, 2026 09:09
@akshaydeo
akshaydeo marked this pull request as ready for review June 7, 2026 09:09
@greptile-apps

greptile-apps Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Confidence Score: 3/5

One changelog file has a factually wrong section header that will be published to users — should be corrected before merge.

The transports/changelog.md ## ✨ Features section was renamed to ## 🔒 Security. The items under it are feature additions (OpenAI Compaction, Multi-Customer Hierarchy, Virtual Key Attribution, etc.), not security changes. Merging as-is will publish a misleading changelog to consumers of the transport module.

transports/changelog.md — the section header needs to be reverted to ## ✨ Features.

Important Files Changed

Filename Overview
transports/changelog.md Section header ## ✨ Features was incorrectly renamed to ## 🔒 Security; the section contains feature additions, not security changes.
core/changelog.md Trailing newline removed from the last line; content unchanged.
core/version Trailing newline removed; version value remains 1.5.17 (PR title says 1.5.7 — likely a title typo).
framework/changelog.md Trailing newline removed; content unchanged.
plugins/governance/changelog.md Trailing newline removed; content unchanged.
plugins/logging/changelog.md Trailing newline removed; content unchanged.
plugins/otel/changelog.md Trailing newline removed; content unchanged.
plugins/compat/changelog.md Trailing newline removed; content unchanged.
plugins/jsonparser/changelog.md Trailing newline removed; content unchanged.
plugins/maxim/changelog.md Trailing newline removed; content unchanged.
plugins/mocker/changelog.md Trailing newline removed; content unchanged.
plugins/prompts/changelog.md Trailing newline removed; content unchanged.
plugins/semanticcache/changelog.md Trailing newline removed; content unchanged.
plugins/telemetry/changelog.md Trailing newline removed; content unchanged.

Reviews (2): Last reviewed commit: "1.5.7 changelogs" | Re-trigger Greptile

@akshaydeo
akshaydeo force-pushed the 05-30-1.5.7_changelogs branch from 20e54cb to a1067b0 Compare June 7, 2026 09:12
@akshaydeo akshaydeo closed this Jun 7, 2026
Comment thread transports/changelog.md
Comment on lines +1 to 3
## 🔒 Security

- **OpenAI Compaction** — Added OpenAI conversation compaction support across core, framework, logging, and the API surface (#4053)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 The section header was changed from ## ✨ Features to ## 🔒 Security, but the items listed under it are feature additions (OpenAI Compaction, Multi-Customer & Org Hierarchy, Provider-Level Governance, Virtual Key Attribution, etc.) — not security changes. Publishing this changelog will misrepresent the release contents for consumers of the transport module.

Suggested change
## 🔒 Security
- **OpenAI Compaction** — Added OpenAI conversation compaction support across core, framework, logging, and the API surface (#4053)
## ✨ Features
- **OpenAI Compaction** — Added OpenAI conversation compaction support across core, framework, logging, and the API surface (#4053)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

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