Release notes
The release workflow writes the GitHub release body from two parts.
The first part is the intro. It's the file in this directory named after the
version, for example 1.5.0.md, and it's optional. Write it before the
chore: update versions pull request is merged, because the workflow reads it
from the commit it publishes.
The second part is the list of changes: the ## Core changes, ## Demo changes
and ## Docs changes sections. pnpm run release-notes builds them from the
three CHANGELOG.md files. Don't write these by hand.
A changeset that bumps several packages ends up in each of their changelogs. The
script shows every entry once. It goes under Core if core is involved, otherwise
under Demo, and otherwise under Docs. The Minor Changes / Patch Changes
split is dropped, so each package gets one flat list.
The workflow also renames the release from @tabler/core@1.5.0 to
Tabler v1.5.0.
What goes in the intro
Follow the earlier releases. Start with a cover image, then add one ## section
per headline feature, with two to four sentences on what it gives the user. Add
a screenshot or a screen recording where it helps.
Images have to be reachable from GitHub. Either upload them to an issue comment
first and paste the user-attachments URL, or commit them next to the intro and
link them by their raw URL on dev:
Link the branch, not the release tag. A tag like @tabler/core@1.5.0 contains a
slash, and raw.githubusercontent.com can't tell it apart from the file path.
For a cover that comes in both color modes, commit the two files and let GitHub pick:
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/tabler/tabler/dev/.github/release-notes/1.5.0-cover-dark.png">
<img alt="Tabler 1.5" src="https://raw.githubusercontent.com/tabler/tabler/dev/.github/release-notes/1.5.0-cover.png">
</picture>
Checking the result
pnpm run release-notes prints the body to stdout, so you can read it before
the release goes out. Pass a path to write it to a file instead.
After the release
docs.tabler.io is built from main. Once the release workflow has published
the new version, run this on dev:
pnpm run release:main
It refreshes the integrity hashes of the CDN snippets in
shared/data/sri.json (they can only be read once the version is on npm),
commits them, pushes dev, then merges dev into main and pushes main. The
merge runs in a temporary worktree, so your checkout stays on dev. Add
--dry-run to stop after the local commit.
Until the hashes are refreshed the docs show the CDN tags without integrity.
That is safe, just less strict. pnpm run check:sri compares the committed
hashes with the CDN if you want to check them by hand.
Fixing a published release
Edit the release on GitHub. The workflow only writes the body once, right after
it publishes, so a later push to dev won't overwrite your edit.