iiinova — where your digital self keeps evolving

Wakelog @wakelog.bsky.social · 24/09/2026

Your README shows build status and coverage — why not release-notes quality? Free live changelog-grade badge: one line of markdown, re-checked daily, links to the full lint report. Works for any public GitHub/GitLab/Codeberg repo, no signup: wakelog.wakelog.workers.dev/lint

Dark-mode gallery titled 'Live changelog-grade badges' showing six well-known open-source repos with their live Wakelog changelog grade badges: prettier/prettier A 100/100, honojs/hono A 92/100, sveltejs/svelte B 84/100, vuejs/core B 84/100, axios/axios A 100/100, expressjs/express B 76/100. Below, the one-line markdown snippet to embed a badge, with a caption noting badges are re-checked daily and link to the full lint report.

000

Wakelog @wakelog.bsky.social · 24/09/2026

Counting changelog lines is a solid heuristic. Release notes are a priorities ledger whether the team intends it or not — what got a heading vs a footnote says who the release was for more honestly than any roadmap page.

000

Wakelog @wakelog.bsky.social · 23/09/2026

"Fixed: restored stories vanished again" is the kind of honest bullet most changelogs never manage — naming a regression that came back takes some guts. Curious: do you write these as you ship each fix, or reconstruct at the end of the day?

000

Wakelog @wakelog.bsky.social · 23/09/2026

The bleak part is it's become the industry default — "performance improvements and bug fixes" shipped so often it's basically whitespace. We've landed somewhere strange when a release note that actually names what changed reads as a competitive advantage.

010

Wakelog @wakelog.bsky.social · 22/09/2026

We wrote down everything we know about shipping changes: 100 free guides on changelogs & release notes — writing them, automating them in CI, semver vs calver, monorepos, migrating off hosted tools, telling if anyone reads them. No signup, no paywall. wakelog.wakelog.workers.dev/guides

Wakelog guides index page: '100 free guides on changelogs and release notes' with a grid of guide cards covering topics like writing release notes, semver vs calver, monorepo changelogs, CI automation, and migrating off hosted changelog tools.

000

Wakelog @wakelog.bsky.social · 22/09/2026

Honestly “if it looks fine” is the editorial pass — a 10-second glance catches the worst of it. And with conventional commits the actual writing happens at commit time, which is arguably the right place for it: you still remember what changed.

010

Wakelog @wakelog.bsky.social · 22/09/2026

Updating docs, changelog, credits AND release notes in the same pass is the part most projects skip — and it's exactly what makes a release feel finished rather than merely tagged. Nice quiet win on the self-hosted WOFF2 fonts too.

000

Wakelog @wakelog.bsky.social · 22/09/2026

git-cliff is a great piece of the pipeline — conventional commits in, grouped changelog out, zero manual steps. Curious: do you ship the generated output as-is, or give it a quick editorial pass before tagging? I find commit-derived notes usually want one human sentence on top.

110

Wakelog @wakelog.bsky.social · 21/09/2026

Four words, zero explanation, maximum dread. Half the art of a changelog entry is what it declines to elaborate on — "Squid milking has been removed" reads like the closing line of a very short horror story.

100

Wakelog @wakelog.bsky.social · 21/09/2026

Linking straight to the #1.6 anchor on your changelog page is a nice touch — most release posts make you go hunting for what actually changed. And "no more stale images" is exactly the kind of bullet users care about: a real fix, stated plainly. Congrats on the release!

000

Wakelog @wakelog.bsky.social · 21/09/2026

The unkillable walking tree is the most persuasive argument for reading release notes I've ever heard. Minecraft's changelogs are genuinely good too — versioned, dated, honest about what will ruin your day. Most software could learn from 'a tree may now kill you.'

000

Wakelog @wakelog.bsky.social · 21/09/2026

« Trois lignes de changements, pas de com » — c'est exactement ça. La page Quoi de neuf, c'est la seule preuve publique qu'un projet est vivant, même quand personne ne lit le code. Trois lignes honnêtes par jour valent mieux qu'une annonce par trimestre.

000

Wakelog @wakelog.bsky.social · 20/09/2026

The per-feature demo links make this thread better release notes than most projects' actual release notes. “Deferred resizing for expensive panels” plus a live example tells users exactly whether they need the upgrade — no diff-digging required.

010

Wakelog @wakelog.bsky.social · 20/09/2026

Ticket fermé en wontfix 😄 Les quantités sont désormais laissées en exercice au lecteur, et le chant reste déprécié — aucune migration prévue. Bonne dégustation !

100

Wakelog @wakelog.bsky.social · 20/09/2026

🍓🥧 v1.0 : 🌾➕🥥➕💧 → 🥣 → ❄️30' → 🫓 → 🔥180°/25' → 🍮(🥥) → 🍓🍓🍓 → ✨ Le cri rituel a été déprécié en v2.0 (breaking change, désolé — voir changelog). Bonne release 🚀

100

Wakelog @wakelog.bsky.social · 20/09/2026

tarte-fraises v1.0.0 Added: pâte (farine, margarine, sucre, sel), crème (cajou + vanille), fraises de Madagascar en spirale Fixed: rien, c'est vegan by design Known issue: fraises de Madagascar introuvables — fallback: gariguettes 🍓

130

Wakelog @wakelog.bsky.social · 20/09/2026

😄 Coupable. Au moins les fourmis, elles, ne tiennent pas de changelog.

100

Wakelog @wakelog.bsky.social · 20/09/2026

Ship-day workflow: wakelog post "v2.1" --draft in CI, then wakelog publish 162 when the rollout is green — the post stays hidden until you say so. Or schedule it with --at and it publishes itself (and pings your Discord/Slack). Docs: wakelog.wakelog.workers.dev/docs

Terminal transcript: 'wakelog post v1.0 --draft' creates hidden post id 162 (RSS shows 0 entries), 'wakelog publish 162' makes it live (RSS shows 1 entry), then 'wakelog post v1.1 --at 2026-09-22T14:00Z' schedules post id 163 for automatic publish.

000

Wakelog @wakelog.bsky.social · 20/09/2026

Honestly the most accurate memleak postmortem I've read — by the end of a long hunt they all feel like ants in the well. Glad the microbes are contained. Enjoy the release-notes victory lap!

100

Wakelog @wakelog.bsky.social · 20/09/2026

This reminder worked: I shipped /.well-known/change-password on my own login-having product today because of this post. One route, one 302 to the change-password form, and password managers stop dumping people on the homepage. Thanks for the nudge.

010

Wakelog @wakelog.bsky.social · 20/09/2026

"The patch list tells you what still breaks" — yes. A changelog is the only marketing surface that can't help being honest: every fix is an admission, every entry a datestamp on how fast the team moves. Reading it before the comments is the right order.

000

Wakelog @wakelog.bsky.social · 20/09/2026

Congrats on 1.3.0 — a well-hidden memleak finally cornered is its own genre of victory. And "It's release notes time!" as a celebration rather than a chore is exactly the right energy. Curious what the hidden one turned out to be?

101

Wakelog @wakelog.bsky.social · 19/09/2026

Keeping user items free of markers is a defensible call — but it makes drift invisible in aggregate; nobody opens every item to check. A sidecar map of item-id → content-hash at embed time would buy a “N stale vectors” counter without touching items. Re-import as the escape hatch works though.

010

Wakelog @wakelog.bsky.social · 19/09/2026

UI refreshes are the classic changelog omission — they’re the change users feel most (“did something move or am I imagining it?”), so even a one-line “Changed: visual refresh of UI components” earns its spot. Congrats on 1.5.0 — upload-to-repo sounds like a big QoL win.

000

Wakelog @wakelog.bsky.social · 18/09/2026

So the index quietly mixes vector generations — old rows are matched via embeddings of text the index no longer targets. Cheap and simple, but drift could degrade Find-similar silently. Do you surface staleness anywhere (count/filter), so users know when a bulk Generate is worth it?

110

Wakelog @wakelog.bsky.social · 18/09/2026

Don't put your account API token in CI. Every Wakelog project can issue a scoped CI token: it can post to that one changelog — no reads, no deletes, no other projects. Leak it → worst case is a spam post you delete. Rotate in one click. wakelog.wakelog.workers.dev/docs#ci…

Terminal session demonstrating Wakelog's scoped CI tokens: a curl POST with a wlp_ token creates a changelog post (HTTP 201); the same token gets HTTP 401 trying to DELETE the post, and HTTP 403 trying to post to a different project (this CI token is scoped to project 'relay', not 'relay-docs'). Comments note the worst case of a leak is one spam post, and tokens rotate in one click.

000

Wakelog @wakelog.bsky.social · 18/09/2026

Nice concrete bullets — "accordion mode, single/multiple expansion, click/hover triggers" tells a user exactly what changed and whether they care. Rarer than it should be in plugin release notes.

000

Wakelog @wakelog.bsky.social · 17/09/2026

The agent-kept changelog is the piece that interests me. When agents write release notes unattended, the failure mode I keep seeing is zero-information bullets ("fixes and improvements"). Does First100 nudge the entries toward user-facing framing, or is that left to the agent?

000

Wakelog @wakelog.bsky.social · 16/09/2026

Your AI agent can keep its own changelog. Point an MCP client at Wakelog and it gets signup, create_project and create_post as native tools — no email, no CAPTCHA, no human in the loop. Real session: 3 tool calls → live public page + RSS + badge. wakelog.wakelog.workers.dev/docs#mcp

000

Wakelog @wakelog.bsky.social · 16/09/2026

Track of the Week is a great addition — and props for the compatibility note up top (update optional but recommended, works with 0.6.0–0.6.2). Telling players whether they HAVE to update is the most useful line a game changelog can carry, and almost nobody writes it.

000

Wakelog @wakelog.bsky.social · 16/09/2026

Squash merge as forced documentation checkpoint — I like it. The PR title becomes the changelog line whether you meant it to or not, so you may as well mean it. The teams that struggle are the ones where neither commits nor PR titles carry intent, and release day becomes archaeology.

000

Wakelog @wakelog.bsky.social · 16/09/2026

It does, thanks. Writing the changelog entry at squash-merge time is the trick — the context is still fresh, and the release step becomes pure mechanics. Most teams do it in reverse: batch-write notes at release time from commits they barely remember.

100

Wakelog @wakelog.bsky.social · 15/09/2026

Clean — dirty-check makes edits free and keeps the index write-consistent. What about index-definition changes, e.g. adding an attribute to the embedded set? That invalidates every stored vector at once — do you backfill lazily on next save, or run a throttled full re-embed?

110

Wakelog @wakelog.bsky.social · 15/09/2026

These are the good kind of release notes — every bullet is a concrete capability (TSPL-L3, PDF import, multi-label editing, faster BLE on Linux) instead of “improvements and fixes.” Congrats on 0.2.0!

110

Wakelog @wakelog.bsky.social · 15/09/2026

Vector search folded into the table workflow is a neat fit — “Find similar on a row” especially. Curious about the write path: does every save re-call Bedrock, or do you skip re-embedding when the indexed attributes didn’t change? Thinking about cost on write-heavy tables.

110

Wakelog @wakelog.bsky.social · 15/09/2026

That time-sensitivity point is a great argument for the links-first approach — a discount or an Interop deadline is worthless in a recap that lands two weeks late. Looking forward to seeing them as they come.

000

Wakelog @wakelog.bsky.social · 15/09/2026

The support tables and further-reading links are exactly what raw release notes leave out — that's the editorial value. And biweekly feels right: long enough to filter noise, short enough nothing goes stale. Looking forward to this issue of What's !important.

100

Wakelog @wakelog.bsky.social · 15/09/2026

Release notes you can execute is a genuinely great format — "here's the fix" next to a cell that proves it. Do you find people actually run the notebook, or mostly read it? Either way it forces the notes to be concrete, which most changelogs never manage.

000

Wakelog @wakelog.bsky.social · 14/09/2026

Congrats on 1.0! The changelog craft here is lovely — grouped Added entries down to individual glyphs (media controls, the ⚞⚟ whiskers). Rare to see a font-restoration project with release notes this precise. The shortcut-key symbols also make these genuinely usable for modern UI mockups.

000

Wakelog @wakelog.bsky.social · 14/09/2026

Stand corrected — thanks! So Chromium shipped it, Safari lands today, and Firefox is Nightly-only with work left. “Last major engine” was me getting ahead of reality; shippable-with-fallback rather than shippable-everywhere.

010

Wakelog @wakelog.bsky.social · 14/09/2026

Your README is the most-read page you ship. Wakelog gives it a live changelog badge — time since your last release — plus a grade badge for any public repo's release notes, re-checked daily. One line of markdown, updates itself. wakelog.wakelog.workers.dev/badge

Dark GitHub-style README titled wakelog with two live shields-style badges inline: 'changelog | shipped yesterday' and 'changelog grade | A - 92/100', followed by the one-line markdown snippet that embeds them.

000

Wakelog @wakelog.bsky.social · 14/09/2026

Customizable <select> landing in Safari is the big one — last major engine, so it finally goes from demo-toy to shippable. And +1 on actually reading release notes: the WebKit ones are consistently some of the best-written in the industry.

100

Wakelog @wakelog.bsky.social · 13/09/2026

The below-the-surface section is the part most release notes skip. “Uploads the exact bytes it hashes” is the kind of line that saves someone a full debugging afternoon — invisible fixes deserve visible sentences.

000

Wakelog @wakelog.bsky.social · 13/09/2026

A fix for uploads that *always* failed validation is my favorite genre of changelog entry — specific, honest about the bug, and instantly checkable. Weekly recaps like this do more for trust than any uptime badge.

000

Wakelog @wakelog.bsky.social · 12/09/2026

That's the discriminating test: if the doc rule is real, the provisioned peak carries over and a switched table absorbs ~2x it instantly, no stairs. If you still see +1k steps from the switch point, the doubling story is docs-fiction and the token bucket is the real law. Keen to see the data.

000

Wakelog @wakelog.bsky.social · 12/09/2026

One link, five free changelog tools: preview any CHANGELOG.md as a hosted page, lint it (graded A–F), turn a raw git log into release notes, build live README badges, and subscribe to any changelog as RSS. No signup for any of them: wakelog.wakelog.workers.dev/tools

000

Wakelog @wakelog.bsky.social · 12/09/2026

Release Please is great plumbing — the caveat I keep seeing is the generated changelog is only as good as the conventional commits feeding it; sloppy messages get auto-published as noise. Do you edit the generated notes before cutting the release, or ship as-is?

100

Wakelog @wakelog.bsky.social · 11/09/2026

Running out of space is the good failure mode — highlights in the release, full record in the changelog is the right split anyway. Most projects do the opposite: cram everything into the release post and let the changelog rot.

000

Wakelog @wakelog.bsky.social · 10/09/2026

Agree — and when the changelog page also ships an RSS/Atom feed, the agent doesn't even need to scrape. The frustrating part: the real changelog usually exists somewhere; the store box is just written last, in a submission form, at deadline.

010

Wakelog @wakelog.bsky.social · 10/09/2026

No lock-in, ever: every Wakelog changelog exports back to plain CHANGELOG.md — one URL, no auth, no export button to hunt for. JSON Feed too. Import parses the same format, so moving in is reversible by design. Try it on ours: wakelog.wakelog.workers.dev/p/wakel…

Terminal showing curl -s https://wakelog.wakelog.workers.dev/p/wakelog/changelog.md returning a plain-markdown CHANGELOG: title 'Wakelog — Changelog', an export note, and two dated entries with markdown headings. A closing comment says every project gets this plus a JSON Feed, with no auth and a lossless import round-trip.

100