Open-source release announcement

A maintainer needs this card per tagged release. Repo name, version, license chip, contributor count. The version string has to be the one on the tag. Nobody should have to remember to edit a “v2.3” text layer.

This is release-time work. The tag is cut. The data file is written from that release. The image is exported from that file. If the version is wrong on the card, the file is wrong, and you can see that in git.

The job is one image written from a data file at release time. You write { repo, version, license, contributors }, you export, you attach the PNG to the release. The next tag is a new file. The component stays put.

Give Lerret a React component under .lerret/ and optional data. export writes a PNG. Same component, data swapped, next image. There is no batch product, no queue, no orchestrator.

The component is .lerret/oss/open-source.jsx. It draws the repo name, the version, the license chip, and the contributor count. The chip is on the component. The version string is in the data. The file lives under .lerret/oss/. Repo, version, license, and contributors are the four fields the card can show, and they all come from the file.

Data is { repo, version, license, contributors } from a data file written at release time. The version string comes from that file, so it is never wrong. Same component, new tag, new file, new image. The contributor count is a field, so it cannot silently stay last tag’s number.

The image is a PNG at 1200×800, the shipped open-source size. One PNG per tagged release, written from the file that was written at release time.

You use Lerret because the version string comes from a file, so it is never wrong. Nobody has to remember to edit the “v2.3” text layer. A design file will keep last tag’s version until someone opens it. A screenshot of the release page will pick up the rest of the page.

npx @lerret/cli@latest export

Start a project with npx create-lerret@latest. More in the use cases index.