bump-libdatadog

Updates libdatadog-dotnet version pins and checksums across CMake and vcpkg build files.

575|168|Updated Aug 30, 2017
One-click install
npx skills add https://github.com/DataDog/dd-trace-dotnet --skill bump-libdatadog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-libdatadog
Source: https://github.com/DataDog/dd-trace-dotnet/tree/main/.claude/skills/bump-libdatadog
Command: npx skills add https://github.com/DataDog/dd-trace-dotnet --skill bump-libdatadog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) components.

What problem does it solve?

Bumping the libdatadog native library in dd-trace-dotnet requires manually updating two version pins and eight SHA-256/SHA-512 hashes across CMake and vcpkg files, which is error-prone and tedious.

Core Features & Use Cases

  • Checksum Fetching: A helper script pulls SHA-256 and SHA-512 checksums directly from the libdatadog-dotnet GitHub release notes via the GitHub API.
  • Guided File Updates: Step-by-step instructions for updating FindLibdatadog.cmake, vcpkg.json, and portfile.cmake with correct version formats (with and without the v prefix).
  • Verification Guidance: Explains how to validate hashes via Nuke build targets and how to handle Alpine symbol snapshot regeneration.
  • Use Case: A maintainer sees a new libdatadog-dotnet release (e.g. v1.3.5) and asks the AI to bump it; the Skill fetches all 8 checksums and updates both platform pins in lockstep.

Quick Start

Ask the AI to bump libdatadog to version 1.3.5 and it will fetch the release checksums and update the CMake and vcpkg files.

Frequently Asked Questions about bump-libdatadog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bump the libdatadog version in dd-trace-dotnet?

Update LIBDATADOG_VERSION and six SHA-256 hashes in build/cmake/FindLibdatadog.cmake, plus the version-string and two SHA-512 hashes in the vcpkg port files. The fetch-release-hashes.sh script retrieves all checksums from the GitHub release notes.

How to fetch libdatadog-dotnet release checksums from GitHub?

Run bash .claude/skills/bump-libdatadog/scripts/fetch-release-hashes.sh <VERSION> without the v prefix. It queries the GitHub API for the release notes and extracts SHA-256 and SHA-512 checksums by hash length.

Does dd-trace-dotnet use upstream DataDog/libdatadog?

No, it consumes DataDog/libdatadog-dotnet, a .NET-specific distribution with a reduced feature set (profiling, crashtracker, symbolizer, library-config). Pin the libdatadog-dotnet release version, not the upstream libdatadog version it was built from.

Why do CMake and vcpkg use different hash types for libdatadog?

The CMake file uses SHA-256 hashes for the six Linux/macOS tarballs, while the vcpkg portfile uses SHA-512 hashes for the two Windows zips. Both checksum sets are published in the libdatadog-dotnet GitHub release notes.

Why does CI fail after a libdatadog version bump?

CI fails if hashes mismatch or if the exported symbol set changed, since Alpine symbol snapshots are verified against checked-in files. Re-run the Alpine symbol validation step and accept the new snapshot if the symbol list changed.