Repository navigation
docs: release 1.7.0 - #88
Merged
Merged
Conversation
iyashjayesh
force-pushed
the
release/v1.7.0
branch
from
August 29, 2026 19:13
3f64d9c to
d1c45f2
Compare
Stamps the eight PRs merged since v1.6.0 as 1.7.0. Four of them fix things a consumer cannot work around: WithOTelEndpoint never sent a metric, profiling was dead in any container without the Go SDK, the health badge contradicted the sentence beside it, and service CPU was inflated by 100/TotalCores. Also regroups the section into one heading per change type. Each PR appended its own "### Fixed" or "### Changed" under [Unreleased] over the day, so the release arrived with eight headings for fourteen bullets.
iyashjayesh
force-pushed
the
release/v1.7.0
branch
from
August 29, 2026 19:14
d1c45f2 to
86eddc6
Compare
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
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.
Stamps the seven PRs merged since v1.6.0 as 1.7.0.
Three fixes a consumer cannot work around
WithOTelEndpointnever sent a metric.Registry,PipelineandMultiExporterwere each implemented and unit-tested, and nothing ever constructed them — so the exporter was created, loggedOTel exporter initialized, and shut down without being asked for anything. Measured against a fake collector: 33 bytes in 40 seconds, all of it gRPC handshake. Anyone who configured OTel export has been receiving nothing, silently.Profiling was dead in production. The profile view shelled out to
go tool pprof, so on any distroless, scratch or alpine image the dashboard returnedError: 'go' command not foundas the report body. Profiles are now parsed in-process; no toolchain, no binary, no source tree.The health badge contradicted itself and flapped. It rendered
Degradedbeside the sentence "System usage is within limits", and crossed the boundary twice in 45 seconds on an idle machine. Also fixed: a single exhausted resource was masked by an idle one, so memory at 104% of its allowance reported as within limits.Also in
Exporters page — Prometheus and OTel status, reported in their own terms. Closes the last entry under "Known gaps".
go getdownloads 25 MB less.monigo.gifwas 24.7 MB of a 25 MB module zip — 96% of every dependency fetch was a README image, and a stale one. Media now lives on theassetsbranch, outside every tagged version.502 MB of committed binaries untracked, with a magic-number test so they cannot return.
The OTel exporter stopped reporting success against an unreachable collector —
Exportnow flushes and returns the transport's verdict.After merge
Tag
v1.7.0and publish.