Skip to content

ci: enable Renovate config migration PRs#6893

Closed
Yicong-Huang wants to merge 1 commit into
mainfrom
renovate/reconfigure
Closed

ci: enable Renovate config migration PRs#6893
Yicong-Huang wants to merge 1 commit into
mainfrom
renovate/reconfigure

Conversation

@Yicong-Huang

Copy link
Copy Markdown
Contributor

What changes were proposed in this PR?

Set configMigration: true in .github/renovate.json5, so that when a config option we use is renamed or deprecated upstream, Renovate opens a PR migrating this file instead of silently logging a warning.

The branch is deliberately named renovate/reconfigure: per the Renovate reconfigure docs, the bot validates the edited config and posts the expected changes as a comment on this PR. This also serves as a liveness probe — Renovate has not processed the repo since .github/renovate.json5 landed in #6848 (the onboarding PR #6855 was closed unmerged shortly before that merge, which flagged the repo as disabled on Mend's side).

Any related issues, documentation, discussions?

Follow-up to #6848; related to onboarding PR #6855.

How was this PR tested?

  • renovate.json5 change validated against the Renovate config schema.
  • Renovate's config validation comment on this PR (once the bot processes it) is the end-to-end check.

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Fable 5)

Set configMigration: true so that when a config option used in
renovate.json5 is renamed or deprecated upstream, Renovate opens a
migration PR instead of silently logging a warning.

The branch is named renovate/reconfigure so the bot posts a config
validation comment on the PR before merge.

Generated-by: Claude Code (Fable 5)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions github-actions Bot added the ci changes related to CI label Jul 25, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Automated Reviewer Suggestions

Based on the git blame history of the changed files, we recommend the following reviewers:

  • No candidates found from git blame history.

@codecov-commenter

codecov-commenter commented Jul 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.97%. Comparing base (7e4a9b4) to head (1145bbf).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #6893      +/-   ##
============================================
- Coverage     77.97%   77.97%   -0.01%     
  Complexity     3661     3661              
============================================
  Files          1161     1161              
  Lines         46059    46059              
  Branches       5105     5105              
============================================
- Hits          35915    35914       -1     
- Misses         8521     8523       +2     
+ Partials       1623     1622       -1     
Flag Coverage Δ *Carryforward flag
access-control-service 70.00% <ø> (ø)
agent-service 76.76% <ø> (ø)
amber 70.67% <ø> (ø) Carriedforward from 7e4a9b4
computing-unit-managing-service 20.49% <ø> (ø)
config-service 66.66% <ø> (ø)
file-service 67.21% <ø> (ø)
frontend 82.64% <ø> (+<0.01%) ⬆️
notebook-migration-service 78.94% <ø> (ø)
pyamber 92.35% <ø> (-0.05%) ⬇️
workflow-compiling-service 55.14% <ø> (ø)

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions

Copy link
Copy Markdown
Contributor

⚠️ Benchmark changes need a look

🟢 2 better · 🔴 3 worse · ⚪ 10 noise (<±5%) · 0 without baseline

Compared against main 7e4a9b4 benchmarked on this same runner, so the delta is largely free of cross-runner hardware noise. The "7d avg" column still reflects the gh-pages dashboard. Treat <±5% as noise unless repeated.

Dashboard · Run

config throughput MB/s latency max Δ latest / 7d
🔴 bs=10 sw=10 sl=64 534 0.326 17,907/25,787/25,787 us 🔴 +8.5% / 🔴 +55.4%
bs=100 sw=10 sl=64 1,125 0.687 86,641/110,706/110,706 us ⚪ within ±5% / 🟢 -16.4%
bs=1000 sw=10 sl=64 1,331 0.813 748,515/789,279/789,279 us ⚪ within ±5% / 🟢 +32.7%
Baseline details

Latest main 7e4a9b4 from same runner

config metric PR latest main 7d avg Δ latest Δ 7d
bs=10 sw=10 sl=64 throughput 534 tuples/sec 582 tuples/sec 754.55 tuples/sec -8.2% -29.2%
bs=10 sw=10 sl=64 MB/s 0.326 MB/s 0.355 MB/s 0.461 MB/s -8.2% -29.2%
bs=10 sw=10 sl=64 p50 17,907 us 16,504 us 12,816 us +8.5% +39.7%
bs=10 sw=10 sl=64 p95 25,787 us 27,168 us 16,594 us -5.1% +55.4%
bs=10 sw=10 sl=64 p99 25,787 us 27,168 us 19,806 us -5.1% +30.2%
bs=100 sw=10 sl=64 throughput 1,125 tuples/sec 1,155 tuples/sec 969.38 tuples/sec -2.6% +16.1%
bs=100 sw=10 sl=64 MB/s 0.687 MB/s 0.705 MB/s 0.592 MB/s -2.6% +16.1%
bs=100 sw=10 sl=64 p50 86,641 us 85,019 us 103,584 us +1.9% -16.4%
bs=100 sw=10 sl=64 p95 110,706 us 110,724 us 109,097 us -0.0% +1.5%
bs=100 sw=10 sl=64 p99 110,706 us 110,724 us 117,304 us -0.0% -5.6%
bs=1000 sw=10 sl=64 throughput 1,331 tuples/sec 1,322 tuples/sec 1,004 tuples/sec +0.7% +32.6%
bs=1000 sw=10 sl=64 MB/s 0.813 MB/s 0.807 MB/s 0.613 MB/s +0.7% +32.7%
bs=1000 sw=10 sl=64 p50 748,515 us 755,427 us 1,002,357 us -0.9% -25.3%
bs=1000 sw=10 sl=64 p95 789,279 us 773,322 us 1,046,463 us +2.1% -24.6%
bs=1000 sw=10 sl=64 p99 789,279 us 773,322 us 1,073,661 us +2.1% -26.5%
Raw CSV
config_idx,batch_size,schema_width,string_len,num_batches,total_ms,total_tuples,total_bytes,tuples_per_sec,mb_per_sec,lat_p50_us,lat_p95_us,lat_p99_us
0,10,10,64,20,374.29,200,128000,534,0.326,17906.62,25787.44,25787.44
1,100,10,64,20,1777.21,2000,1280000,1125,0.687,86641.08,110705.58,110705.58
2,1000,10,64,20,15021.35,20000,12800000,1331,0.813,748514.97,789279.36,789279.36

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

Labels

ci changes related to CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants