| name | release-blog-post |
| description | Generate the announcement blog post (and LinkedIn image) for a new Selenium 4.x release, by scaffolding from the previous post, summarizing the GitHub changelog, sorting contributors, and compositing the release image. Use when a new Selenium version (e.g. 4.41) has just been released and needs its blog post. |
Release blog post
Produces the selenium-4-N-released.md post and its selenium_4.N.jpg share image for a
freshly released Selenium version, following the same structure as previous posts under
website_and_docs/content/blog/*/selenium-4-*-released.md.
Run every step from the repo root. Ask the user for the new version (e.g. 4.41) if it
isn't already known — everything else below is derived from it.
1. Scaffold
scripts/release-updates.sh 4.41
This, for version 4.41 (previous = 4.40):
- Bumps
4.40.x → 4.41.0 (and the adjacent human-readable release date) in
website_and_docs/layouts/partials/selenium-clients-and-webdriver-bindings.html and
website_and_docs/layouts/downloads/list.html.
- Copies the previous release's blog post to
website_and_docs/content/blog/<year-of-release>/selenium-4-41-released.md, git adds it,
replaces 4.40 → 4.41 throughout, and sets date: to the selenium-4.41.0 tag's commit
date (the year is derived the same way, so this works across year boundaries).
- Prints three deduped, sorted
{{< gh-user ... >}} lists — Selenium, Docs, and Docker
contributors — for commits between the selenium-4.40.0 and selenium-4.41.0 tags.
Everything after this point is manual editing of the new blog file using the data gathered
in the remaining steps. The copied file still has the release's prose and
contributor lists — all of it needs replacing, not just the version string.
