Release foundations 5.7.2 and foundations-sentry 1.1.0#214
Merged
Conversation
fisherdarling
approved these changes
Jun 5, 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.
foundations 5.7.2
EncodeMetricimplementation returns anErrresult at runtime don't cause the/metricsendpoint to return a 500 status code anymore. Instead, a wrapper inside foundations swallows the error and logs it at WARN level. The output is rewound to the last written newline to ensure it remains OpenMetrics compliant.foundations-sentry 1.1.0
foundations_sentry::panic::NoFlushPanicIntegrationis a variant of sentry's default panic handler integration which emits the same events, but without an explicit flush after each panic. This significantly reduces the time spent inside the panic handler, but at the cost of losing events if the process aborts due to double-panic.