Description
The source-build release-day PR template expects both $RUNTIME_VERSION and $RELEASE_DATE, but eng/pipeline/source-build-release/steps/re-bootstrap.yml only exports SDK_VERSION and derives RELEASE_DATE from the agent's current date.
This produces PR bodies with a missing runtime version:
The 2026-08B test runs also generated July titles because they ran on July 31 even though their releaseDate parameter was 2026-08-11:
Root cause
source-build-release-pr.md uses $RUNTIME_VERSION and $RELEASE_DATE. The Open PR step in re-bootstrap.yml never exports RUNTIME_VERSION and sets RELEASE_DATE=$(date +"%B %Y") instead of using the pipeline's expected release date.
Suggested fix
Pass the existing runtimeVersion job variable and pipeline releaseDate parameter through source-build-base.yml -> stages/public-release.yml -> jobs/public-release-sdk.yml -> steps/re-bootstrap.yml, then export both values before envsubst. Add a focused check that renders the PR template with a future release date and a runtime version.
This issue was filed with the help of AI. It might be incorrect.
Description
The source-build release-day PR template expects both
$RUNTIME_VERSIONand$RELEASE_DATE, buteng/pipeline/source-build-release/steps/re-bootstrap.ymlonly exportsSDK_VERSIONand derivesRELEASE_DATEfrom the agent's current date.This produces PR bodies with a missing runtime version:
Source-build updates for the .NET / 8.0.129 July 2026 release.Source-build updates for the .NET / 9.0.119 July 2026 release.The 2026-08B test runs also generated July titles because they ran on July 31 even though their
releaseDateparameter was2026-08-11:Root cause
source-build-release-pr.mduses$RUNTIME_VERSIONand$RELEASE_DATE. TheOpen PRstep inre-bootstrap.ymlnever exportsRUNTIME_VERSIONand setsRELEASE_DATE=$(date +"%B %Y")instead of using the pipeline's expected release date.Suggested fix
Pass the existing
runtimeVersionjob variable and pipelinereleaseDateparameter throughsource-build-base.yml->stages/public-release.yml->jobs/public-release-sdk.yml->steps/re-bootstrap.yml, then export both values beforeenvsubst. Add a focused check that renders the PR template with a future release date and a runtime version.This issue was filed with the help of AI. It might be incorrect.