docs: update 4.x branch for v4.11.0 release (take 2) #4434
Merged
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
This is a workaround for `npm ci` failing with:
Invalid: lock file's [email protected] does not satisfy [email protected]
Closes: #4396
….57.0 in test fixtures(#4385)
…cker digest to fc17dbf (#4376)
…rks (#4398) v3.723.0 and later of some aws-sdk-js v3 clients updated to use `@smithy/smithy-client@4` which is part of what is instrumented.
…s arguments (#4400) ./dev-utils/update-4x-branch.sh [TARGTAG [LASTTAG]] Passing TARGTAG is needed when the HEAD commit is no longer the tagged release commit. Passing LASTTAG is necessary if the 4.x branch wasn't updated for a particular release.
An alternative to https://github.com/integrations/slack for Slack notifications for issue/PR actions. Refs: elastic/elastic-otel-node#496 This switches to the older form of styling Slack 'attachments' eschewing the newer 'blocks', which don't style quite as nicely IMHO.
…cker digest to f2813ac (#4402)
This is (a) to avoid the warnings in workflow runs, e.g.:
test-tav (@apollo/server 22) ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see actions/runner-images#10636
and (b) to try it out ahead of the switch.
Updates `cookie` from 0.6.0 to 0.7.2 Updates `light-my-request` from 6.0.0 to 6.5.1
…n't have one (#527) (#4414) This fixes a 'SlackError: Missing input!' error when skipping a notification, e.g. for a dependabot PR: https://github.com/elastic/elastic-otel-node/actions/runs/12743214047/job/35512726091?pr=526 Refs: elastic/elastic-otel-node#527
…mental Next.js instrumentation (#4415) The next.js instrumentation is experimental and support is locked to an old/deprecated version of Next.js and is unlikely to move forward from there. There is no value in dependabot updates for this test app.
The 'request' library is long since deprecated. I'm tired of the security warnings for its deps.
#4406) Bumps the github-actions group with 1 update: [docker/build-push-action](https://github.com/docker/build-push-action). Updates `docker/build-push-action` from 6.10.0 to 6.11.0 - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@48aba3b...b32b51a)
@opentelemetry/core: 1.30.0 -> 1.30.1 @opentelemetry/resources: 1.30.0 -> 1.30.1 @opentelemetry/sdk-metrics: 1.30.0 -> 1.30.1 @opentelemetry/exporter-prometheus: 0.57.0 -> 0.57.1
…cker digest to ea157dd (#4424)
…4426) See https://learn.microsoft.com/en-ca/azure/azure-functions/functions-node-upgrade-v4 This builds on the work in #4178 by @qzxlkj, which provide most of the runtime code fix. The rest of this is adding testing and updated examples and docs. Refs: #4178 Closes: #3185
david-luna
approved these changes
Jan 20, 2025
This was referenced Jan 20, 2025
Merged
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.
Refs: #4432 (release PR)