Skip to content

ci(release): accept multiple crates in release-proposal-dispatch#2012

Open
iunanua wants to merge 2 commits into
mainfrom
igor/versioning/multi-crate-proposal
Open

ci(release): accept multiple crates in release-proposal-dispatch#2012
iunanua wants to merge 2 commits into
mainfrom
igor/versioning/multi-crate-proposal

Conversation

@iunanua
Copy link
Copy Markdown
Contributor

@iunanua iunanua commented May 19, 2026

Summary

  • Replace the single-choice crate input with a crates string input that accepts comma- or whitespace-separated names.
  • Add a validate-inputs job that normalizes (split → dedupe → sort), validates each name against publishable workspace members via cargo metadata, and rejects multi-crate + hotfix combinations up front.
  • Branch segment collapses to <first>+<N-1>-more when more than one crate is selected; existing release/*/* globs in release-proposal-test.yml and the gitlab branch filter continue to match.

🤖 Generated with Claude Code

Replace the single-choice `crate` input with a `crates` string input
that accepts comma/whitespace-separated names, validated up front against
publishable workspace members. Hotfix releases still require a single
crate. Branch names collapse to `<first>+<N-1>-more` when more than one
crate is selected; the PR title preserves the existing
`chore(release): proposal for ` prefix.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@iunanua iunanua requested a review from a team as a code owner May 19, 2026 14:41
SC2001 (line 80): replace `sed 's/^/  - /' <<< "$AVAILABLE"` with
`printf '  - %s\n' "${AVAILABLE[@]}"` by making AVAILABLE an array; the
membership check uses `printf | grep -qxF` accordingly.

SC2170 (line 826): expose `validate-inputs.outputs.count` through the
step's existing `env:` block as `$CRATES_COUNT` so shellcheck sees a
shell variable instead of a literal `${{ ... }}` in the numeric test.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.69%. Comparing base (78a55c8) to head (b3b5e1a).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2012      +/-   ##
==========================================
- Coverage   72.75%   72.69%   -0.07%     
==========================================
  Files         452      452              
  Lines       74895    74930      +35     
==========================================
- Hits        54489    54467      -22     
- Misses      20406    20463      +57     
Components Coverage Δ
libdd-crashtracker 65.31% <ø> (-0.02%) ⬇️
libdd-crashtracker-ffi 37.56% <ø> (ø)
libdd-alloc 98.77% <ø> (ø)
libdd-data-pipeline 85.90% <ø> (-0.61%) ⬇️
libdd-data-pipeline-ffi 73.93% <ø> (ø)
libdd-common 79.81% <ø> (ø)
libdd-common-ffi 74.41% <ø> (ø)
libdd-telemetry 73.37% <ø> (+0.02%) ⬆️
libdd-telemetry-ffi 31.36% <ø> (ø)
libdd-dogstatsd-client 82.64% <ø> (ø)
datadog-ipc 76.22% <ø> (ø)
libdd-profiling 81.69% <ø> (ø)
libdd-profiling-ffi 64.79% <ø> (ø)
libdd-sampling 97.46% <ø> (ø)
datadog-sidecar 28.87% <ø> (-0.02%) ⬇️
datdog-sidecar-ffi 8.56% <ø> (ø)
spawn-worker 48.86% <ø> (ø)
libdd-tinybytes 93.16% <ø> (ø)
libdd-trace-normalization 81.71% <ø> (ø)
libdd-trace-obfuscation 87.30% <ø> (-0.10%) ⬇️
libdd-trace-protobuf 68.25% <ø> (ø)
libdd-trace-utils 89.59% <ø> (ø)
libdd-tracer-flare 86.88% <ø> (ø)
libdd-log 74.83% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@datadog-prod-us1-6
Copy link
Copy Markdown

datadog-prod-us1-6 Bot commented May 19, 2026

Pipelines  Tests

Fix all issues with BitsAI

⚠️ Warnings

🚦 2 Pipeline jobs failed

Release - Open a release proposal PR | check-membership   View in Datadog   GitHub Actions

🛟 This job is unlikely to succeed on retry. Please review your pipeline configuration. Permission denied while fetching resource. Error: HTTP status: 403.

Release - Open a release proposal PR | validate-inputs   View in Datadog   GitHub Actions

See error Error: unknown or unpublishable crate(s): libdd-telem. Available crates: libdd-alloc, libdd-capabilities, libdd-capabilities-impl, libdd-common, libdd-crashtracker, libdd-data-pipeline, libdd-ddsketch, libdd-dogstatsd-client, libdd-http-client, libdd-library-config, libdd-log, libdd-profiling, libdd-profiling-protobuf, libdd-sampling, libdd-shared-runtime, libdd-telemetry, libdd-tinybytes, libdd-trace-normalization, libdd-trace-obfuscation, libdd-trace-protobuf, libdd-trace-stats, libdd-trace-utils.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 72.69% (+0.01%)

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: b3b5e1a | Docs | Datadog PR Page | Give us feedback!

@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented May 19, 2026

Artifact Size Benchmark Report

aarch64-alpine-linux-musl
Artifact Baseline Commit Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 81.76 MB 81.76 MB 0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so 7.57 MB 7.57 MB 0% (0 B) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.01 MB 10.01 MB 0% (0 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 97.95 MB 97.95 MB 0% (0 B) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 24.47 MB 24.47 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib 79.87 KB 79.87 KB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb 180.01 MB 180.02 MB +0% (+8.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 913.25 MB 913.25 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 7.73 MB 7.73 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib 79.87 KB 79.87 KB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb 23.15 MB 23.15 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 45.34 MB 45.34 MB 0% (0 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 21.09 MB 21.09 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib 81.11 KB 81.11 KB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb 184.23 MB 184.22 MB -0% (-8.00 KB) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 898.95 MB 898.95 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 5.99 MB 5.99 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib 81.11 KB 81.11 KB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb 24.80 MB 24.80 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 42.85 MB 42.85 MB 0% (0 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 72.86 MB 72.86 MB 0% (0 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 8.42 MB 8.42 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 90.62 MB 90.62 MB 0% (0 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.06 MB 10.06 MB 0% (0 B) 👌

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.

2 participants