Repository navigation
release(chore): date the untagged 1.3.0 release 2026-10-12 - #87
Conversation
1.3.0 was prepared on 2026-10-07 but has not shipped, and it now also carries usage, low-quota alerts and the Raycast extension. Move the CHANGELOG heading and the dates the GEO test ties to it: the homepage dateModified and footer, the llms.txt release line, and both sitemap lastmod entries. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The release date is synchronized across the listed release and site materials. No merge-blocking issue is evident. Pre-merge checks |
|
Summary
1.3.0 was prepared on 2026-10-07 but hasn't shipped: the release dry run fails at the npm sign-in check (
NPM_TOKEN). Since then it has also picked upusage, low-quota alerts and the Raycast extension (#82–#85). This updates its date to 2026-10-12 everywhere the site test ties it to:CHANGELOG.md: the## 1.3.0 - …headingdocs/index.html:dateModifiedand the footer's "Last updated"docs/llms.txt: the current-release linedocs/sitemap.xml: bothlastmodentriesNo version, checksum or
bin/codex-profilechanges. If the release slips past this date, these six spots need to move together again.Testing
node test/site/geo-test.mjspasses.make checkpasses (exit 0, including ShellCheck).Scope and compatibility
Checklist
make check; if the environment lacks ShellCheck, I ranmake testand documented the missing lint result instead.app defaultsession and use the original signed app bundle.🤖 Generated with Claude Code
Summary by CodeRabbit