* chore(release): add v1.0.9 changelog, customer email, and thumbnail artifacts
* chore(release): rewrite v1.0.9 customer email as a webhook announcement
* chore(release): tighten v1.0.9 email around what people asked for
* chore(release): rewrite v1.0.9 email around webhook value
* chore(release): write a plain v1.0.9 webhook announcement email
* chore(release): close v1.0.9 email with a G2 review ask
* chore(release): add v1.0.8 changelog, customer email, and thumbnail artifacts
* chore(release): sharpen the v1.0.8 email and encode the rules in /release
The subject and section headers named areas (Facebook Pages, Asset
Library) instead of what got better, so a subscriber could not tell
from the inbox what the release did for them.
- Lead on the widest-reach change (Business Portfolio Pages) rather
than the newest one, and match the section order to the subject
- Say plainly that Asset Library reuse is new for the API and MCP
only, since the in-app path already worked
- Drop the four bullets that repeated a theme section verbatim
- Reorder the thumbnail chips to follow the sections
.claude/commands/release.md carries the same rules so the next release
starts there: subject pattern, ordering by reach, the already-existed-
in-app trap, header wording, and no duplication between prose and lists.
* chore(release): add v1.0.7 changelog, customer email, and thumbnail artifacts
* chore(release): use a friendlier generic thumbnail headline for v1.0.7
Add a 1200x630 changelog thumbnail as a fourth release artifact, generated
from a shared brand template that mirrors the marketing-site hero / OG image:
warm cream to lavender wash, ink dot-grid, an Instrument Serif headline with a
hand-drawn violet squiggle, a segmented 'CHANGELOG | <version>' sticker badge,
and colored ink-bordered theme chips with solid offset shadows.
- .claude/release-assets/: render-thumbnail.mjs (Playwright renderer),
thumbnail.template.html (brand template), logo.png (TryPost wordmark)
- .claude/commands/release.md: new Step 5b renders the thumbnail; it is
versioned in the artifacts PR alongside the changelog and email
- releases/v1.0.6/thumbnail.png: image for the latest release
Tweak the /release command's email template (GitHub release link in the byline,
"Paulo from TryPost.it" signature) and add the generated v1.0.2 release notes.
Removed the logic that conditionally seeds the UserSeeder based on the self-hosting configuration. This simplifies the DatabaseSeeder and assumes user data will be handled externally.
Refines the /release slash command to streamline the weekly release process, ensuring better detection of version bumps and integration with the GitHub release API for automated note generation and email drafting.
