Repository navigation
fix(release-calendar): add 2026-09-23.0 and date 2026-09-23.1 as a patch - #572
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The calendar entries match the issue requirements and established patch-release structure.
0 open findings
What changed in this PR
Restores accurate release-calendar metadata for the September 2026 initial and patch releases.
Changes:
- Adds the missing
2026-09-23.0release. - Dates patch
2026-09-23.1to its September 25 shipment.
| File | Description |
|---|---|
static/release-calendar.json |
Records both September 2026 releases with schema version v2.0.0. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
🗺️ Overture Docs preview is live!
Note ♻️ This preview updates automatically with each push to this PR. |
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
Alex Iannicelli (atiannicelli)
left a comment
Alex Iannicelli (atiannicelli)
left a comment
There was a problem hiding this comment.
k
#547 bumped the September row to
2026-09-23.1in place, so the.0release (still live in S3 and the STAC catalog) had noschemaVersionin the calendar. This adds the.0row back dated2026-09-23and moves the.1row to2026-09-25, when the GERS ID patch shipped. Matches how the2025-03-19.0/.1pair is recorded.Closes #571.