chore(deps): bump galileo-core to ^4.5.0 - #630
Merged
Merged
Conversation
galileo-core 4.5.0 adds the `extra_headers` field that the custom HTTP headers feature (#629) relies on. Pinning the minimum to 4.5.0 ensures a fresh resolve can't pick a core release that silently ignores GALILEO_EXTRA_HEADERS (the getattr fallbacks would no-op and a gateway would just 401). Addresses Fernando's post-merge follow-up on #629. Co-Authored-By: Claude <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #630 +/- ##
=======================================
Coverage 83.62% 83.62%
=======================================
Files 124 124
Lines 11037 11037
=======================================
Hits 9230 9230
Misses 1807 1807 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
![baz-reviewer[bot]](https://avatars.githubusercontent.com/in/933528?s=60&v=4){kind=small}
fercor-cisco
approved these changes
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User description
What
Bumps the
galileo-coredependency constraint from^4.4.0→^4.5.0(both the main and test/testing-extra entries) and regeneratespoetry.lock.Why
The custom HTTP headers feature merged in #629 relies on
galileo-core's newextra_headersconfig field (now released in galileo-core 4.5.0, from orbit #1376). Until this bump,pyproject.tomlstill allowed^4.4.0, so a fresh resolve could lock to a core release withoutextra_headers— in which case settingGALILEO_EXTRA_HEADERSsilently no-ops on every egress path (thegetattr(config, "extra_headers", None)fallbacks inlogger.py/traces.pydegrade toNone, and core-backed calls omit the headers), and a gateway like IBM APIC just returns 401 — a hard-to-diagnose failure.Raising the minimum to
4.5.0makes the dependency match the feature's actual requirement.This addresses the non-blocking post-merge follow-up Fernando (@fercor-cisco) raised on #629.
Notes / follow-up
extra_headers, the defensivegetattr(config, "extra_headers", None)fallbacks inlogger.py/traces.pycould be simplified to direct attribute access. Left as a separate change to keep this PR a pure dependency bump.Testing
poetry check --lock→All set!galileo-coreversion/hash and the metadata content-hash (regenerated with the same Poetry 2.2.0 that produced the existing lock, so no unrelated marker churn).🤖 Generated with Claude Code
Generated description
Below is a concise technical summary of the changes proposed in this PR:
Raise the
galileo-coredependency constraint inpyproject.tomlso the core SDK and itstestingextra resolve to a release that providesextra_headers. Regeneratepoetry.lockto pingalileo-core4.5.0and keep dependency resolution aligned.Latest Contributors(2)