Patch Notes Table
A dense patch table listing version, date, a type chip, and a one line summary per row, closed by a note on the versioning policy.
A dense patch table listing version, date, a type chip, and a one line summary per row, closed by a note on the versioning policy.
Search blocks by description or jump to a page.
The source for every Marketing block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Patch Notes Table puts the small releases on the record. A dense table lists every patch by version and date with a type chip, Fix, Security, or Performance, and a one line summary of what changed. The header pairs the intent with a link to the release feed, and a closing line states the versioning promise, that patches never change behavior and never need a migration.
The patches are one array of version, date, type, and summary, with a palette keyed to the type so the chips read consistently down the column. Write each summary as the effect a user would notice rather than the internal fix, exports respect the workspace timezone beats timezone refactor, and keep the list to the releases since the last minor so the table stays current.
Reach for this block on a changelog page beneath the headline releases, where the incremental fixes and security work still deserve a home. A table is the honest format for the small stuff, one line each, no ceremony, and it signals a team that ships steadily between the big announcements. It sits below the depth of release-notes-columns and catches everything the whats-new-banner never mentions.
A natural flow around it on a Marketing Pro page:
Before
After
One strong use is every patch since the last minor release. Other tables:
Tip: keep the type chips to a short fixed set, a table with eight different labels loses the scannability a table is for.