Skip to content

feat: schedule cross-language LTO post for 2026-05-01 (Friday)#39

Merged
avrabe merged 1 commit into
mainfrom
feat/blog-cross-lang-lto-schedule
Apr 27, 2026
Merged

feat: schedule cross-language LTO post for 2026-05-01 (Friday)#39
avrabe merged 1 commit into
mainfrom
feat/blog-cross-lang-lto-schedule

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented Apr 27, 2026

Summary

New blog post added to the auto-publish queue:

  • File: `content/blog/2026-05-01-cross-language-lto-three-quiet-barriers.md`
  • Title: Cross-language LTO on Cortex-M: three barriers and a wrong prediction
  • Frontmatter: `date = 2026-05-01` (Friday), `draft = true`, no `hold` flag
  • Renamed from `2026-05-02-*` to match the new date

The daily 06:00 UTC autopublish cron will:

Local scanner verified end-to-end:

```
"scheduled": [
...
{ "slug": "cross-language-lto-three-quiet-barriers",
"date": "2026-05-01", "draft": true, "hold": false }
]
```

Test plan

  • zola build clean (drafts excluded — still 23 pages)
  • Scanner output confirms placement in Scheduled bucket
  • CI passes
  • After merge: tomorrow's cron run shows the post under Scheduled on issue Blog auto-publish status #36
  • On 2026-05-01: cron auto-publishes, deploy follows

🤖 Generated with Claude Code

Move the post into the auto-publish queue: rename file from
2026-05-02-* to 2026-05-01-* (Friday, May 1) and update frontmatter
date to match. Frontmatter:

  date  = 2026-05-01
  draft = true
  hold  unset

Once this lands on main, the daily 06:00 UTC autopublish cron will
list it as Scheduled in issue #36 and flip draft = false on the
morning of 2026-05-01.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@avrabe avrabe merged commit 084558e into main Apr 27, 2026
1 check passed
@avrabe avrabe deleted the feat/blog-cross-lang-lto-schedule branch April 27, 2026 05:38
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.

1 participant