chore(deps): bump opentelemetry-sdk from 1.41.1 to 1.44.0 - #116
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps): bump opentelemetry-sdk from 1.41.1 to 1.44.0#116dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [opentelemetry-sdk](https://github.com/open-telemetry/opentelemetry-python) from 1.41.1 to 1.44.0. - [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-python@v1.41.1...v1.44.0) --- updated-dependencies: - dependency-name: opentelemetry-sdk dependency-version: 1.44.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Collaborator
|
Closing: this makes
The OTel packages have to move as a set, via |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dgokeeffe
added a commit
that referenced
this pull request
Aug 5, 2026
#120) CI has never run the test suite on this repo. The Tests workflow has exactly one run in its history — a manual workflow_dispatch in May — and that run has zero jobs. Dependency Audit and Update Lockfile have never produced a run at all. Cause: all three target `databrickslabs-protected-runner-group`. That group is granted per-repo across the org (ucx, dqx, dlt-meta and others use it successfully) and this repo was never granted it, so jobs targeting it are never scheduled — silently, with no failure anywhere to notice. Consequences already observed: - #84 bumped pydantic-core to 2.47.0 while pydantic==2.13.4 pins pydantic-core==2.46.4 exactly. requirements.txt became unsatisfiable, so every Databricks Apps deploy from main failed until #110 repaired it. GitHub reported the PR MERGEABLE; nothing installed requirements.txt. - #115 and #116 were the same failure and were caught only by resolving them by hand. - requirements.lock had drifted from requirements.txt, because Update Lockfile never ran. Regenerated here. ## Runners test.yml, dependency-audit.yml and update-lockfile.yml move to ubuntu-latest. None of them need org secrets — the first two are read-only, and the third uses only the repo-scoped GITHUB_TOKEN. GitHub-hosted runners are free for public repos. release.yml is left on the protected group: it signs release artifacts, so it deserves a deliberate decision rather than a drive-by change (it also means releases stay blocked until the repo is granted the group — noted in the PR). ## New gates, each tied to a failure that actually happened 1. requirements.txt must be installable — catches the #84/#115/#116 class. 2. requirements.lock must match requirements.txt — catches the drift above. 3. App modules must import — 13 modules whose failure takes the app down at boot, most with no direct unit test. 4. A floor on tests that actually ran — a suite reporting "all skipped" passes vacuously, which is exactly what #106 fixed (465 skipped). ## Two bugs found while verifying the workflow locally - tests/e2e/conftest.py raised an uncaught FileNotFoundError when the databricks CLI is absent. That surfaces as a pytest INTERNALERROR which kills the entire session — so this workflow would have failed on its first run on a hosted runner, where the CLI isn't installed. A missing CLI is now treated as "prerequisite absent" and skips. - tests/integration is excluded from the PR gate. It gates on Docker, and Docker *is* present on ubuntu-latest, so it would really run: building an apps-like image and executing the full setup pipeline. Confirmed locally that including it produces failures. It stays runnable on demand. ## Verification Every step was run locally, including with PATH stripped of the databricks CLI to simulate a hosted runner: 535 passed, 3 skipped. Each of the four gates was then confirmed to fail when its bug is reintroduced — the #84 pin, a truncated lockfile, and the #106 whole-session skip.
dgokeeffe
added a commit
that referenced
this pull request
Aug 5, 2026
#120) CI has never run the test suite on this repo. The Tests workflow has exactly one run in its history — a manual workflow_dispatch in May — and that run has zero jobs. Dependency Audit and Update Lockfile have never produced a run at all. Cause: all three target `databrickslabs-protected-runner-group`. That group is granted per-repo across the org (ucx, dqx, dlt-meta and others use it successfully) and this repo was never granted it, so jobs targeting it are never scheduled — silently, with no failure anywhere to notice. Consequences already observed: - #84 bumped pydantic-core to 2.47.0 while pydantic==2.13.4 pins pydantic-core==2.46.4 exactly. requirements.txt became unsatisfiable, so every Databricks Apps deploy from main failed until #110 repaired it. GitHub reported the PR MERGEABLE; nothing installed requirements.txt. - #115 and #116 were the same failure and were caught only by resolving them by hand. - requirements.lock had drifted from requirements.txt, because Update Lockfile never ran. Regenerated here. ## Runners test.yml, dependency-audit.yml and update-lockfile.yml move to ubuntu-latest. None of them need org secrets — the first two are read-only, and the third uses only the repo-scoped GITHUB_TOKEN. GitHub-hosted runners are free for public repos. release.yml is left on the protected group: it signs release artifacts, so it deserves a deliberate decision rather than a drive-by change (it also means releases stay blocked until the repo is granted the group — noted in the PR). ## New gates, each tied to a failure that actually happened 1. requirements.txt must be installable — catches the #84/#115/#116 class. 2. requirements.lock must match requirements.txt — catches the drift above. 3. App modules must import — 13 modules whose failure takes the app down at boot, most with no direct unit test. 4. A floor on tests that actually ran — a suite reporting "all skipped" passes vacuously, which is exactly what #106 fixed (465 skipped). ## Two bugs found while verifying the workflow locally - tests/e2e/conftest.py raised an uncaught FileNotFoundError when the databricks CLI is absent. That surfaces as a pytest INTERNALERROR which kills the entire session — so this workflow would have failed on its first run on a hosted runner, where the CLI isn't installed. A missing CLI is now treated as "prerequisite absent" and skips. - tests/integration is excluded from the PR gate. It gates on Docker, and Docker *is* present on ubuntu-latest, so it would really run: building an apps-like image and executing the full setup pipeline. Confirmed locally that including it produces failures. It stays runnable on demand. ## Verification Every step was run locally, including with PATH stripped of the databricks CLI to simulate a hosted runner: 535 passed, 3 skipped. Each of the four gates was then confirmed to fail when its bug is reintroduced — the #84 pin, a truncated lockfile, and the #106 whole-session skip.
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
1 participant
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 opentelemetry-sdk from 1.41.1 to 1.44.0.
Changelog
Sourced from opentelemetry-sdk's changelog.
... (truncated)
Commits
53a5a40Prepare release 1.44.0/0.65b0 (#5422)d9f34e7Fixup eachdist.py handling of package names (#5417)d10f472opentelemetry-semantic-conventions: Bump to 1.43.0 (#5413)ae8feebUpdate otelbot token workflows to use client IDs (#5404)67a2abdFix Context in-place mutability bypass via inherited dict methods (#5399)87baad9Bump semconv to 1.42.0 (#5410)23dc0b2opentelemetry-sdk: add 'force_flush' method to LogRecordExporter ABC (#5294)bec55fdopentelemetry-sdk: expose SynchronousMultiLogRecordProcessor and ConcurrentMu...55d0b7aopentelemetry-sdk: Add ability to refresh process sensitive Resource attribut...6115db2opentelemetry-sdk: add log record limits environment variables (#5300)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)