chore(chart): bump node-agent image to 0.1.2, chart to 0.1.11 - #522
Merged
Conversation
Picks up the otel exporter startup fix (nudgebee/node-agent#293): agent fataled on plain-HTTP TRACES_ENDPOINT since the otel v1.43 bump. New immutable image tag 0.1.2 instead of republishing 0.1.1, whose in-place republish on 2026-07-10 caused the CrashLoopBackOff incident.
Contributor
|
📦 Image Tags Updated |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
blue4209211
approved these changes
Jul 15, 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.
Bumps
nodeAgent.image.tagto0.1.2and the chart to0.1.11.Picks up nudgebee/node-agent#293 (otel exporter startup fatal on plain-HTTP
TRACES_ENDPOINTsince the otel v1.43 bump). Completes the incident fix started in #521 — chart 0.1.10 fixed the entrypoint but still points at the broken0.1.1image, so fresh pulls crashloop on the otel bug.Do not merge until:
v0.1.2is tagged on node-agent main and the release workflow publishesghcr.io/nudgebee/node-agent:0.1.2New immutable tag
0.1.2instead of republishing0.1.1— the in-place republish of0.1.1on 2026-07-10 is what caused the incident.