Skip to content

chore(deps): update datadog-api-client digest to d774d3c - #818

Closed
dd-octo-sts[bot] wants to merge 1 commit into
mainfrom
engraver-auto-version-upgrade/renovate/datadog-api-client-digest
Closed

dd-octo-sts[bot] wants to merge 1 commit into
mainfrom
engraver-auto-version-upgrade/renovate/datadog-api-client-digest

Conversation

@dd-octo-sts

@dd-octo-sts dd-octo-sts Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
datadog-api-client dependencies digest 68fea12d774d3c

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

@dd-octo-sts

dd-octo-sts Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --workspace
info: syncing channel updates for 1.95.0-aarch64-unknown-linux-gnu
info: latest update on 2026-04-16 for version 1.95.0 (59807616e 2026-04-14)
info: downloading 7 components
    Updating crates.io index
warning: spurious network error (3 tries remaining): [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)
warning: spurious network error (2 tries remaining): [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)
warning: spurious network error (1 try remaining): [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)
    Updating git repository `https://github.com/DataDog/datadog-api-client-rust`
From https://github.com/DataDog/datadog-api-client-rust
 * [new ref]           d774d3c8e676904a7422d613dfd18bf99e7cc98c -> refs/commit/d774d3c8e676904a7422d613dfd18bf99e7cc98c
error: failed to get `dirs` as a dependency of package `pup v1.19.1 (/tmp/renovate/repos/github/DataDog/pup)`

Caused by:
  download of config.json failed

Caused by:
  failed to download from `https://index.crates.io/config.json`

Caused by:
  [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)

@dd-octo-sts
dd-octo-sts Bot marked this pull request as ready for review September 14, 2026 19:37
@dd-octo-sts
dd-octo-sts Bot requested a review from a team as a code owner September 14, 2026 19:37
@dd-prapprover-prod-77c48c

dd-prapprover-prod-77c48c Bot commented Sep 14, 2026

Copy link
Copy Markdown

PRApprover will approve and merge this PR, FAQ, #dx-source-code-management

🛠️ PRApproval Status

  • ✅ PR is eligible for auto-approval by rule dependency-management-renovate-updater - 2026-09-14T19:38:29Z
  • ⬜ CI tests passed
  • ⬜ Approved
  • ⬜ Merge Started
  • ⬜ Merged

➡️ Current phase: CI tests failed. Please fix the failing tests and rerun the workflow, click Workflow Link -> Workflow Starter Link -> Start Workflow

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Datadog Autotest: FAIL

The manifest pins the new client revision, but Cargo.lock still pins the old revision. This mismatch breaks locked builds.

Open Bits AI session

🤖 Datadog Autotest · Commit 58a1242 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest

Comment thread Cargo.toml
# Datadog API client — pinned to 0.33.0 tag
# Use default-features = false; feature sets are activated per-target via features above
datadog-api-client = { git = "https://github.com/DataDog/datadog-api-client-rust", rev = "68fea1224e7ce303787b842811103b99c6406cf4", optional = true, default-features = false }
datadog-api-client = { git = "https://github.com/DataDog/datadog-api-client-rust", rev = "d774d3c8e676904a7422d613dfd18bf99e7cc98c", optional = true, default-features = false }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Update Cargo.lock for the new client revision

Locked builds fail, and unlocked builds change the committed dependency graph.

Assertion details
  • Input: Build the pull request with Cargo lock enforcement, such as cargo --locked or cargo --frozen.
  • Expected: Cargo.lock must resolve datadog-api-client at revision d774d3c8 after the manifest revision changes.
  • Actual: Cargo.lock still resolves datadog-api-client at revision 68fea122. Cargo rejects locked dependency resolution or rewrites the tracked lockfile without locked mode.

Was this helpful? React 👍 or 👎
🤖 Datadog Autotest · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest · Open Bits AI session

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant