Bump nodejs from v2.6.1 to v2.7.0 in helm-charts/splunk-otel-collector/values.yaml #1143
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
update-nodejs
branch
from
12fcacd to
6876427
Compare
github-actions
bot
force-pushed
the
update-nodejs
branch
from
6876427 to
8382835
Compare
|
The splunk-otel-js release v2.7.0 was created but it looks like the Docker image for this release still hasn't been created (related Github Action). |
|
The missing splunk-otel-js image issue has been fixed. Looks like the functional tests do have a legit failure, the root cause is likely the same issue affecting other current open PRs. |
github-actions
bot
force-pushed
the
update-nodejs
branch
4 times, most recently
from
2a5646e to
0b4ca92
Compare
jinja2
approved these changes
Feb 7, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Use the latest version of nodejs