Skip to content

feat: automate release status in schedule#258

Merged
robobario merged 1 commit into
kroxylicious:mainfrom
robobario:release-schedule-auto-released
May 18, 2026
Merged

feat: automate release status in schedule#258
robobario merged 1 commit into
kroxylicious:mainfrom
robobario:release-schedule-auto-released

Conversation

@robobario
Copy link
Copy Markdown
Member

Convert release schedule from static HTML to data-driven Liquid templating. Status now automatically changes from "Planned" to "Released" when a release YAML file appears in _data/release/, eliminating manual updates when releases are published.

Assisted-by: Claude Sonnet 4.5 noreply@anthropic.com

Screenshot From 2026-05-18 16-47-44

Convert release schedule from static HTML to data-driven Liquid
templating. Status now automatically changes from "Planned" to
"Released" when a release YAML file appears in _data/release/,
eliminating manual updates when releases are published.

Assisted-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Signed-off-by: Robert Young <robertyoungnz@gmail.com>
@robobario robobario requested a review from a team as a code owner May 18, 2026 04:48
Copy link
Copy Markdown
Member

@SamBarker SamBarker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Getting there. I still wonder if we can drive it directly from the github milestone dates?

@robobario
Copy link
Copy Markdown
Member Author

Getting there. I still wonder if we can drive it directly from the github milestone dates?

Will look into it, it would be cool if creating/editing a milestone would cause a PR to be created here.

@robobario robobario merged commit 45704bc into kroxylicious:main May 18, 2026
2 checks passed
@robobario
Copy link
Copy Markdown
Member Author

robobario commented May 18, 2026

Also, I currently don't think there's a good way to figure out the canonical "release date", the per release files don't contain that currently. It's one that could also get out of sync between creating the release PRs and hitting merge.

Thinking it might be better if the Column was called "Release Date" and already released ones display their release date, and planned ones put their intended date from the schedule.

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.

2 participants