Skip to content

Automate post-release baseline propagation and gate on nuget indexing#307

Merged
Vulthil merged 2 commits into
mainfrom
ci/baseline-propagation
Jul 9, 2026
Merged

Automate post-release baseline propagation and gate on nuget indexing#307
Vulthil merged 2 commits into
mainfrom
ci/baseline-propagation

Conversation

@Vulthil

@Vulthil Vulthil commented Jul 9, 2026

Copy link
Copy Markdown
Owner

Summary

  • Gate release.yml's baseline-bump PR on nuget.org having indexed the released version, so its restore doesn't race indexing and fail with NU1102.
  • Add a propagate-baseline-to-main job that, after a servicing-branch release, bumps main's PackageValidationBaselineVersion to match — upward only, and skipped entirely when the release is dispatched from main itself.
  • Catch up main's baseline to 1.0.2 now, since the last servicing release never propagated here.

Verification

  • Ran eng/propagate_baseline.py against scratch Directory.Build.props copies for all four scenarios (newer/older/equal/missing-property).
  • actionlint on the changed workflow: no new findings.
  • dotnet build -c Release succeeds against the 1.0.2 baseline.

Backport to v1.0: yes — release workflows execute per-branch; companion PR #308

@claude

claude Bot commented Jul 9, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

@Vulthil
Vulthil merged commit ad9764e into main Jul 9, 2026
6 checks passed
@Vulthil
Vulthil deleted the ci/baseline-propagation branch July 9, 2026 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant