release
Skill9.1k starsChanged todayMITView on GitHub
How Instatic is released, and what an agent must check before letting a release go out. Releases fire on a pushed `v*` tag and are fully automated by GitHub Actions. Covers the pre-tag preparation PR, building the changelog from merged PRs, the tag push, what Actions does afterwards, and the ordering rule that security advisories publish last. Use this skill when a maintainer asks to cut, prepare, or publish a release, when a version needs bumping, when a changelog section needs creating, or when checking whether main is releasable.
- Commits and pushes
193 other projects use a version of this.
Trending
Less talk lately.about the whole repository
Most recently taken up by
- coredevices/PebbleOStheir own version, first seen Nov 16, 2026
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
Who's talking about CoreBunch/Instatic
- @github-trending-js.bsky.social“🔥 Hot Repo! 🔥 (100+ new stars) 📦 CoreBunch / Instatic ⭐ 3,852 (+176) 🗒 TypeScript Instatic is a modern …”Bluesky · Jul 24, 2026 · 4 likes
- @github-trending-js.bsky.social“🎉 Celebrating! 🎉 (500+ new stars) 📦 CoreBunch / Instatic ⭐ 6,043 (+700) 🗒 TypeScript The open-source …”Bluesky · Jul 27, 2026 · 2 likes
- A Hacker News story“Instatic is a modern self-hosted visual CMS”Hacker News · Jun 30, 2026 · 2 points
- @github-trending.bsky.social“🔥 Hot Repo! 🔥 (100+ new stars) 📦 CoreBunch / Instatic ⭐ 4,051 (+179) 🗒 TypeScript The open-source …”Bluesky · Jul 24, 2026 · 1 likes
- @github-trending-js.bsky.social“🚀 Skyrocketing! 🚀 (200+ new stars) 📦 CoreBunch / Instatic ⭐ 1,348 (+351) 🗒 TypeScript Instatic is a …”Bluesky · Jul 1, 2026 · 1 likes
The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 18
Talked about on GitHub, Bluesky and Hacker News (18 times).
On GitHub · 12
- Nov 10, 2026[catalog-candidate] instatic-self-hosted-cms — ePlus-DEV/free-tier-hub0 reactions · 3 comments
- Nov 8, 2026Research: evaluate Instatic as page builder / publisher for storefront pages — Viora-Tech/e-commerce0 reactions
- Sep 23, 2026feat(ai/drivers): Requesty-driver landen vanuit upstream PR #243 — 0xtsotsi/Instatic0 reactions
- Sep 8, 2026Instatic vs Sveltia — sveltia/sveltia-cms0 reactions
- Aug 7, 2026idea: CoreBunch/Instatic — zqf1314/idea0 reactions · 1 comment
7 more on GitHub
- Aug 6, 2026Publish v0.0.14 — bradleybeatz1313/release-pagekeeper-sandbox0 reactions
- Jul 27, 2026CoreBunch Instatic: 에이전트 주도형 셀프호스팅 비주얼 CMS — roomedia/ax-trend0 reactions
- Jul 27, 2026Github trending [CoreBunch/Instatic] 自托管 CMS 一键部署 — web1992/github-trending0 reactions
- Jul 26, 2026🔥 GitHub Trending AI 早报 · 2026-07-27 · Top 4 项目 — happydog-intj/ai-xiaohongshu-daily0 reactions
- Jul 26, 2026🔥 GitHub Trending AI 早报 · 2026-07-27 · Top 4 项目 — Mystery406/ai-xiaohongshu-daily0 reactions
- Jul 26, 2026🔥 GitHub Trending AI 晚报 · 2026-07-26 · Top 4 项目 — Mystery406/ai-xiaohongshu-daily0 reactions
- Jul 26, 2026🔥 GitHub Trending AI 晚报 · 2026-07-26 · Top 4 项目 — happydog-intj/ai-xiaohongshu-daily0 reactions
On Bluesky · 5
- Jul 24, 2026🔥 Hot Repo! 🔥 (100+ new stars) 📦 CoreBunch / Instatic ⭐ 3,852 (+176) 🗒 TypeScript Instatic is a modern self-hosted visual CMS - get it… — @github-trending-js.bsky.social4 likes and reposts
- Jul 27, 2026🎉 Celebrating! 🎉 (500+ new stars) 📦 CoreBunch / Instatic ⭐ 6,043 (+700) 🗒 TypeScript The open-source alternative to Webflow, Framer and… — @github-trending-js.bsky.social2 likes and reposts · 1 reply
- Jul 24, 2026🔥 Hot Repo! 🔥 (100+ new stars) 📦 CoreBunch / Instatic ⭐ 4,051 (+179) 🗒 TypeScript The open-source alternative to Webflow, Framer and… — @github-trending.bsky.social1 likes and repost
- Jul 1, 2026🚀 Skyrocketing! 🚀 (200+ new stars) 📦 CoreBunch / Instatic ⭐ 1,348 (+351) 🗒 TypeScript Instatic is a modern self-hosted visual CMS - get… — @github-trending-js.bsky.social1 likes and repost · 1 reply
- Jun 30, 2026🚀 Skyrocketing! 🚀 (200+ new stars) 📦 CoreBunch / Instatic ⭐ 1,348 (+351) 🗒 TypeScript Instatic is a modern self-hosted visual CMS - get… — @github-trending.bsky.social1 likes and repost · 1 reply
On Hacker News · 1
- Jun 30, 2026Instatic is a modern self-hosted visual CMS2 points
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- instatic-user-e2eSkill
- maintainSkill
- run-and-testSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Ask the maintainer for the version if it was not supplied.
- Distinctive: line 46
Write one entry per user-visible outcome, not necessarily one per PR: a PR that fixes two unrelated symptoms gets two entries, and a …
- Distinctive: line 62
Before committing the section, reread it as a user who has never seen the code.
- Very specific: line 64
Create the new dated section at the top of CHANGELOG.md and order its headings:
- Very specific: line 103
When the non-versioned template configuration changed, copy the two Render blueprints into their template repositories as root render.yaml:
- Distinctive: line 120
Every entry is one or two sentences, in product words, with no root-cause mechanics or internal names.
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Releasing Instatic
The version lives in package.json and releases are tag-triggered. .github/workflows/release.yml fires on v*.*.*, and everything it publishes is built from whatever main looked like at that tag. There is no undo: a pushed tag builds and pushes images to GHCR and creates a GitHub Release. Get main right first.
The full maintainer reference is docs/deployment/release-workflow.md. This skill is the agent's operating procedure around it; when the two disagree, the doc wins and this file needs updating.
Never tag without being asked
Cutting a release is the maintainer's decision, not an inference from "the work looks done". Prepare, present, and wait. Pushing a tag is the single most irreversible action in this repo.
Step 1 — Establish the release range and version
git tag --sort=-version:refname | head -3 # last shipped
grep -m1 '"version"' package.json
head -12 CHANGELOG.mdThe latest release tag is the lower bound. The release preparation covers everything merged into main after that tag and nothing still sitting in an open PR.
Ask the maintainer for the version if it was not supplied. Never invent the number: patch versus minor is a judgement about impact, and it is theirs.
Step 2 — Build the changelog from merged PRs
Changelog authoring happens here, not in feature or fix PRs. Start from the PRs merged into main since the latest release tag. Use GitHub's merged-PR data as the roster and reconcile it with the commit range so direct commits or unusual merge strategies cannot disappear.
git log v<last>..origin/main --oneline
gh pr list --state merged --base main --limit 200 \
--json number,title,body,mergedAt,url,labels,mergeCommitFor every PR whose merge commit falls in that range, inspect the PR body and the merged diff. Record either its changelog entry or the concrete reason it has no user-visible release impact. Account for direct commits in the range the same way. Internal refactors, test-only changes, documentation, CI, and dependency bumps with no user-visible effect normally earn no entry.
How to write an entry
The changelog is read by people deciding whether to upgrade, not by the people who wrote the code. A PR body argues a change to a reviewer; a changelog entry tells a user what is different. They are different documents, and pasting the first into the second is the failure mode to avoid.
One or two sentences per entry. Hard limit. A fix gets one sentence for what was broken and is now fixed. A feature gets one sentence for what it does, and at most a second for the part a user would otherwise have to discover. If an entry needs more than that, the detail belongs in the feature doc under docs/, and the entry can point there.
Write one entry per user-visible outcome, not necessarily one per PR: a PR that fixes two unrelated symptoms gets two entries, and a feature split across three PRs gets one.
What belongs in an entry:
- The symptom a user recognises. "A device that signed in seconds ago could read as hours old", not "SQLite writes
YYYY-MM-DD HH:MM:SSand V8 parses that shape as local time". - What they can now do, in the words they would use for it. "Share a preview link with someone who has no admin account."
- Plain nouns from the product, not from the codebase. Panels, pages, plugins, publishing. Not modules, comparators, adapters, or relays.
What never belongs:
- Root-cause mechanics, function and file names, internal type or module names, migration IDs, capability strings, test counts, line counts.
- The engineering argument for the approach taken, alternatives rejected, or why the change was scoped as it was.
- Anything a user cannot see, act on, or verify.
Use past tense for what was fixed and present tense for what the product now does. Name and credit security advisories when applicable; those entries may run longer, because a GHSA is read by someone assessing exposure and needs the affected surface and the precondition stated.
Before committing the section, reread it as a user who has never seen the code. Any sentence that only makes sense if you have is a sentence to cut.
Create the new dated section at the top of CHANGELOG.md and order its headings:
### Features### Bug fixes### Security### Other changes
Omit empty headings. Put behavior changes and user-visible maintenance that are neither features nor fixes under Other changes. If an undated section remains from the former rolling-changelog workflow, treat it only as input: rebuild the release section from the merged-PR roster and remove duplicates or entries for unmerged work.
Step 3 — The preparation PR
One PR, titled chore(release): prepare <version>, containing exactly:
| File | Change |
CHANGELOG.md | add the complete dated release section built from merged PRs: ## <version> - <YYYY-MM-DD> |
package.json | version bumped to match |
docs/deployment/README.md | version-pinned image tag |
docs/deployment/docker-image.md | version-pinned image tag |
docs/deployment/railway.md | version-pinned image tag |
Those three docs deliberately pin a semver image tag and go stale silently, which is why they are listed rather than left to memory. The Render blueprints stay on :latest; scripts/build-release-bundle.ts rewrites the bundle copies to the semver tag automatically.
Nothing else belongs in this PR. Merge it before tagging so the tag points at a commit describing the release it is.
Step 4 — Tag, once approved
git checkout main && git pull
git tag v<version>
git push origin v<version>Actions then runs bun run build, bun test, bun run lint, builds the Dockerfile, pushes ghcr.io/corebunch/instatic at <semver>, <major>.<minor> and latest, creates the GitHub Release, and uploads instatic-<version>-release-bundle.tar.gz plus the per-platform instatic-server-<version>-<platform>.tar.gz server artifacts.
Watch it. A tag whose verify job fails has still moved the tag, so the fix is a new patch version rather than a retag.
Step 5 — After the image is published
When the non-versioned template configuration changed, copy the two Render blueprints into their template repositories as root render.yaml:
corebunch/instatic-render-sqlite
corebunch/instatic-render-postgresSecurity advisories publish last
The release workflow fires only on tags. A GHSA published before its fix is tagged and imaged announces a vulnerability that users cannot yet upgrade away from. Order is: prepare, tag, wait for the image to appear on GHCR, then publish the advisory.
GHSA metadata for this repo uses ecosystem: other and names the GHCR image, not an npm package.
Before you present the release
mainis green on the gate fromrun-and-test.- The changelog section is dated, built from every PR merged since the latest release tag, grouped with features before bug fixes, and contains no unmerged work.
- Every entry is one or two sentences, in product words, with no root-cause mechanics or internal names. Reread the section as a user who has never seen the code.
package.jsonmatches the version.- The three deployment docs pin the new tag.
- Any security advisory is drafted but not published.
- A maintainer has said to tag it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

