-
Notifications
You must be signed in to change notification settings - Fork 60
Implement automated release workflow with scheduled GitHub Actions and issue templates #1960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
@ClaudiaComito 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs. I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review. |
…ed GitHub Actions Co-authored-by: ClaudiaComito <39374113+ClaudiaComito@users.noreply.github.com>
Co-authored-by: ClaudiaComito <39374113+ClaudiaComito@users.noreply.github.com>
|
Add to workflow:
|
| on: | ||
| schedule: | ||
| # 2 weeks before Easter (approximately March 15th) | ||
| - cron: '0 9 15 3 *' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - cron: '0 9 15 3 *' | |
| - cron: '0 9 12 3 *' |
for release date March 26th 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in commit 7fffd84. Changed cron schedule to '0 9 12 3 *' for March 12 (2 weeks before March 26 release).
| # 2 weeks before Easter (approximately March 15th) | ||
| - cron: '0 9 15 3 *' | ||
| # 2 weeks before Christmas (approximately December 15th) | ||
| - cron: '0 9 15 12 *' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - cron: '0 9 15 12 *' | |
| - cron: '0 9 3 12 *' |
for release date Dec 17 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in commit 7fffd84. Changed cron schedule to '0 9 3 12 *' for Dec 3 (2 weeks before Dec 17 release).
|
|
||
| on: | ||
| schedule: | ||
| # 2 weeks before Easter (approximately March 15th) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # 2 weeks before Easter (approximately March 15th) | |
| # 2 weeks before March 26 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in commit 7fffd84. Comment now reads "2 weeks before March 26".
| schedule: | ||
| # 2 weeks before Easter (approximately March 15th) | ||
| - cron: '0 9 15 3 *' | ||
| # 2 weeks before Christmas (approximately December 15th) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # 2 weeks before Christmas (approximately December 15th) | |
| # 2 weeks before Dec 17 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in commit 7fffd84. Comment now reads "2 weeks before Dec 17".
| # 4 weeks before Easter (approximately March 1st) | ||
| - cron: '0 9 1 3 *' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # 4 weeks before Easter (approximately March 1st) | |
| - cron: '0 9 1 3 *' | |
| # 4 weeks before March 26 | |
| - cron: '0 9 26 2 *' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in commit 7fffd84. Changed to '0 9 26 2 *' for Feb 26 (4 weeks before March 26 release).
| # 4 weeks before Christmas (approximately December 1st) | ||
| - cron: '0 9 1 12 *' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # 4 weeks before Christmas (approximately December 1st) | |
| - cron: '0 9 1 12 *' | |
| # 4 weeks before Dec 17 | |
| - cron: '0 9 19 11 *' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in commit 7fffd84. Changed to '0 9 19 11 *' for Nov 19 (4 weeks before Dec 17 release).
- Updated release dates to March 26 and Dec 17 (from Easter/Christmas approximations) - Adjusted all workflow cron schedules accordingly: - release-schedule: 4 weeks before (Feb 26, Nov 19) - release-code-freeze: 2 weeks before (Mar 12, Dec 3) - release-notes-finalization: 1 week before (Mar 19, Dec 10) - Added "Select cover figure" task to blog post preparation workflow and template Co-authored-by: ClaudiaComito <39374113+ClaudiaComito@users.noreply.github.com>
Added in commit 7fffd84. The "select cover figure" task is now included in:
|
This PR implements the improved release workflow proposal from issue #1959, introducing automated preparation tasks for Heat's bi-annual release schedule.
Overview
The implementation adds comprehensive automation for release preparation while preserving human oversight for critical decisions. The system follows a structured timeline leading up to scheduled releases on March 26th (Spring) and December 17th (Winter).
Key Features
🤖 Automated Workflows
Release Schedule (
release-schedule.yml)pr-talkfor release discussionCode Freeze (
release-code-freeze.yml)Release Notes Finalization (
release-notes-finalization.yml)📋 Issue Templates
Five new structured templates for release preparation:
Each template includes:
🏷️ Label Organization
release-prep- All automated preparation issuespr-talk- PRs requiring release discussioncode-freeze-review- PRs under freeze evaluationcompliance,highlights,citation,blog-posthigh-priority,critical📚 Documentation Updates
RELEASE.mdwith automation detailsTechnical Implementation
Benefits
Integration
The automation handles the preparation phase while preserving the existing manual release process for actual publication. This ensures human oversight remains in place for critical decisions while eliminating repetitive administrative tasks.
Workflows can be triggered manually for off-schedule releases, and individual issue templates can be used independently when needed.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.