GitHub: Update pull request template with next release dates.
What changed, and why it matters
This commit simply updates the dates in the GitHub pull request template for the next software release cycle. It changes no code, no configuration, and no security-related documentation. There is no security issue here.
No action required. This is a routine project-management documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies only .github/PULL_REQUEST_TEMPLATE.md, replacing release freeze, RC1, and final release dates for the 25.09 cycle with dates for the 25.12 cycle. No source code, build scripts, CI configuration, or security controls are touched.
Changed components
Inspect captured patch +3 / −3
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 86fb2f3c..f33ae33d 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,10 +1,10 @@
> [!IMPORTANT]
>
-> 25.09 FREEZE July 28TH: Non-bugfix PRs not ready by this date will wait for 25.12.
+> 25.12 FREEZE October 27th: Non-bugfix PRs not ready by this date will wait for 26.03.
>
-> RC1 is scheduled on _August 11th_
+> RC1 is scheduled on _November 10th_
>
-> The final release is scheduled for September 1st.
+> The final release is scheduled for December 1st.
## Checklist
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.