Skip to content

Comments

[Automation] Bump product version numbers#2639

Merged
shainaraskas merged 3 commits intomainfrom
updatecli_main_bfbda0570cfbf1ebee5ba4801497a4b00fe1289653863b5c09f26db4b8c67c6e
Feb 6, 2026
Merged

[Automation] Bump product version numbers#2639
shainaraskas merged 3 commits intomainfrom
updatecli_main_bfbda0570cfbf1ebee5ba4801497a4b00fe1289653863b5c09f26db4b8c67c6e

Conversation

@elastic-observability-automation
Copy link
Contributor

Bump release versions in the config/versions.yml

Update config/versions.yml elasticsearch-client-javascript 9.3.0

change detected: * key "$.versioning_systems.elasticsearch-client-javascript.current" updated from "9.2.1" to "9.3.0", in file "config/versions.yml"

v9.3.0
[Changelog](https://www.elastic.co/docs/release-notes/elasticsearch/clients/javascript#elasticsearch-javascript-client-9.3.0-release-notes)
Update config/versions.yml edot-node 1.8.0

change detected: * key "$.versioning_systems.edot-node.current" updated from "1.7.0" to "1.8.0", in file "config/versions.yml"

v1.8.0
## Changelog

### Fixes

* Fix the handling of the `deactivate_all_instrumentations` [central configuration](elastic-otel-node://reference/edot-node/configuration.md#central-configuration) setting. If the value is `false`, it is now treated the same as if the setting had not been specified in central configuration. This means that `deactivate_all_instrumentations=false` and `deactivate_instrumentations=foo` will result in the "bar" instrumentation *not* being deactivated, which is the intended behavior. Before this change, `deactivate_all_instrumentations=false` would result in the `deactivate_instrumentations` setting being completely ignored. [#1236](https://github.com/elastic/elastic-otel-node/issues/1236)

### Chores

* Update all `@opentelemetry/*` upstream package dependencies to the latest releases:
    - [`v2.5.0` release](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.5.0) from opentelemetry-js
    - [`experimental/v0.211.0` release](https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.211.0) from opentelemetry-js
    - [opentelemetry-js-contrib releases](https://github.com/open-telemetry/opentelemetry-js-contrib/releases) up to 2026-01-22

---

[README](https://github.com/elastic/elastic-otel-node/tree/main/packages/opentelemetry-node#readme) | [Full Release Notes](https://github.com/elastic/elastic-otel-node/blob/main/docs/release-notes/index.md) | [Breaking Changes](https://github.com/elastic/elastic-otel-node/blob/main/docs/release-notes/breaking-changes.md)
Update config/versions.yml apm-agent-go 2.7.3

change detected: * key "$.versioning_systems.apm-agent-go.current" updated from "2.7.2" to "2.7.3", in file "config/versions.yml"

v2.7.3
## What's Changed
* docs: Use h3 consistently for env var docs by @carsonip in https://github.com/elastic/apm-agent-go/pull/1777
* Updating major.minor versions docs by @hegerchr in https://github.com/elastic/apm-agent-go/pull/1778
* Upgrade Go SDK because of CVE-2026-24051 by @dmathieu in https://github.com/elastic/apm-agent-go/pull/1781

## New Contributors
* @hegerchr made their first contribution in https://github.com/elastic/apm-agent-go/pull/1778

**Full Changelog**: https://github.com/elastic/apm-agent-go/compare/v2.7.2...v2.7.3
GitHub Action workflow link
Updatecli logo

Created automatically by Updatecli

Options:

Most of Updatecli configuration is done via its manifest(s).

  • If you close this pull request, Updatecli will automatically reopen it, the next time it runs.
  • If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made.

Feel free to report any issues at github.com/updatecli/updatecli.
If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

@shainaraskas shainaraskas merged commit 9fcf07c into main Feb 6, 2026
32 of 33 checks passed
@shainaraskas shainaraskas deleted the updatecli_main_bfbda0570cfbf1ebee5ba4801497a4b00fe1289653863b5c09f26db4b8c67c6e branch February 6, 2026 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant