release-version
Skill1.8k starsChanged 7 days agoApache-2.0View on GitHub
Recommend the next release version of a Kubetail component (cli, dashboard, cluster-api or cluster-agent) under SemVer 2.0.0. Use when asked which version to release or tag next.
10 other projects use a version of this.
Trending
Less talk lately.about the whole repository
Most recently taken up by
- Nucs/Agentmastertheir own version, first seen Nov 13, 2026
- foldkit/foldkittheir own version, first seen Nov 2, 2026
- ngthluu/my-dev-skillstheir own version, first seen Nov 1, 2026
- cachewraith/cachewraith-skillstheir own version, first seen Oct 25, 2026
- crux-cli/cruxtheir own version, first seen Oct 13, 2026
- corvo007/MioSubtheir own version, first seen Oct 8, 2026
Who's talking about kubetail-org/kubetail
- A Hacker News story“Show HN: Kubetail – Real-time log search for Kubernetes”Hacker News · May 1, 2025 · 126 points
- A Hacker News story“Show HN: Kubetail – Web-based real-time log viewer for Kubernetes”Hacker News · Feb 13, 2024 · 70 points
- @damyr.fr“Sur Kube tu as github.com/kubetail-org..., mais le graph d'event manque faut avouer”Bluesky · May 26, 2025 · 4 likes
- @matsuu.bsky.social“k8sのログをブラウザ経由で参照できるダッシュボード実装。pod単位のほか、deploymentやdaemonsetの単位で複数Podのログをまとめてのリアルタイム表示もできる。正規表現による絞り込みも可。”Bluesky · May 4, 2025 · 4 likes
- @chrisshort.net“kubetail-org/kubetail: Real-time logging dashboard for Kubernetes. View logs in a terminal or a browser. …”Bluesky · May 22, 2026 · 1 likes
The biggest 5 of 27 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 27
Talked about on GitHub, Bluesky and Hacker News (27 times).
On GitHub · 20
- Oct 24, 2025🐋 Release kubetail-0.15.4 — kubetail-org/helm-charts1 reaction
- Oct 22, 2026chore(deps): update kubetail to v0.18.1 — uniget-org/tools0 reactions · 2 comments
- Jul 13, 2026💎 Knowledge Update & Optimization: 13 Jul 2026 — nubenetes/awesome-kubernetes0 reactions · 40 comments
- Jul 12, 2026💎 Knowledge Update & Optimization: 12 Jul 2026 — nubenetes/awesome-kubernetes0 reactions · 40 comments
- Jul 12, 2026💎 Knowledge Update & Optimization: 12 Jul 2026 — nubenetes/awesome-kubernetes0 reactions · 40 comments
15 more on GitHub
- Jun 25, 2026x/vulndb: potential Go vuln in github.com/kubetail-org/kubetail/modules/cli: GHSA-v8j7-hp7c-738f — golang/vulndb0 reactions · 1 comment
- Feb 5, 2026feat(kubetail): add package — brioche-dev/brioche-packages0 reactions
- Dec 8, 2025add kubetail — ai-solution-eng/frameworks0 reactions
- Oct 4, 2025feat: add kubetail plugin — asdf-vm/asdf-plugins0 reactions
- Sep 28, 2025Add kubetail plugin — kubernetes-sigs/krew-index0 reactions · 8 comments
- Sep 26, 2025new naming conflict with a project — johanhaleby/kubetail0 reactions · 2 comments
- Sep 19, 2025dev-util/kubetail-bin: add 0.7.5, 0.8.2 — gentoo/gentoo0 reactions · 6 comments
- Sep 18, 2025[Request]: kubetail — ScoopInstaller/Main0 reactions · 1 comment
- Jul 11, 2025🎣 Patch release — kubetail-org/helm-charts0 reactions
- Jul 9, 2025Add Real-Time Log Streaming with Kubetail — kubestellar/ui0 reactions · 5 comments
- Jun 21, 2025TypeScript definitions missing in v8 — nmn/react-timeago0 reactions · 1 comment
- May 21, 2025kubetail-org/kubetail: 一个通用的 Kubernetes 日志仪表板,可以暴漏在浏览器当中查看。 — awesome-ops/awesome-ops.github.io0 reactions
- May 20, 2025Integrate Kubetail graphical Logs for pods and jobs into Kubestellar — kubestellar/ui0 reactions · 9 comments
- May 2, 2025Vendoring a package using "local" imports from another directory? — openSUSE/obs-service-go_modules0 reactions
- Feb 2, 2025new addon: kubetail — kubernetes/minikube0 reactions · 26 comments
On Bluesky · 5
- May 26, 2025Sur Kube tu as github.com/kubetail-org..., mais le graph d'event manque faut avouer — @damyr.fr4 likes and reposts · 1 reply
- May 4, 2025k8sのログをブラウザ経由で参照できるダッシュボード実装。pod単位のほか、deploymentやdaemonsetの単位で複数Podのログをまとめてのリアルタイム表示もできる。正規表現による絞り込みも可。 — @matsuu.bsky.social4 likes and reposts
- May 22, 2026kubetail-org/kubetail: Real-time logging dashboard for Kubernetes. View logs in a terminal or a browser. Run anywhere - desktop, cluster,… — @chrisshort.net1 likes and repost
- May 1, 2025Show HN: Kubetail – Real-time log search for Kubernetes Hi Everyone! Kubetail is a general-purp... https://github.com/kubetail-org/kubetail… — @kubernetes.activitypub.awakari.com.ap.brid.gy1 likes and repost
- Feb 13, 2024Show HN: Kubetail – Web-based real-time log viewer for Kubernetes Discussion — @hn100.bsky.social1 likes and repost
On Hacker News · 2
- May 1, 2025Show HN: Kubetail – Real-time log search for Kubernetes126 points · 35 comments
- Feb 13, 2024Show HN: Kubetail – Web-based real-time log viewer for Kubernetes70 points · 33 comments
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- foldkit/foldkit★ 1.1ksame name
- corvo007/Gemini-Subtitle-Pro★ 835same name
- corvo007/MioSub★ 835same name
- Byte-n/larkDocx2md★ 34same name
- hhhyyyy99/prot-skills★ 7same name
- Vochsel/dump.page★ 3same name
- ngthluu/my-dev-skills★ 2same name
- Nucs/Agentmaster★ 1same name
- cachewraith/cachewraith-skills★ 0same name
- crux-cli/crux★ 0same name
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 repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- crates/CLAUDE.mdCLAUDE.md
- dashboard-ui/CLAUDE.mdCLAUDE.md
- e2e/CLAUDE.mdCLAUDE.md
- modules/CLAUDE.mdCLAUDE.md
- proto/CLAUDE.mdCLAUDE.md
- release-cliSkill
- release-clusterSkill
- release-notesSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 58
Read each commit's body as well (git log --format=%B -1 <sha>) for a BREAKING CHANGE: or BREAKING-CHANGE: footer.
- Distinctive: line 61
If the list is empty, say there is nothing to release and stop.
- Very specific: line 115
If that gives X.Y.Z or lower, X.Y.Z already holds these changes.
- Very specific: line 118
If it gives a higher version, the changes outgrow X.Y.Z: recommend that higher version, and offer its first prerelease (-rc.1) beside it.
- Very specific: line 126
The old form (
rc1): Every prerelease tagged so far uses it (dashboard/v0.17.0-rc3). - Very specific: line 131
Never recommend build metadata (+…).
- Very specific: line 142
Check too that the tag does not exist yet (git rev-parse -q --verify refs/tags/<tag> prints nothing) and that it sorts above the last …
“Common” is measured: kept by at least 6 in 10 of the 9 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
Recommend the next release version
Recommend the next version of one component, given as the argument: cli, dashboard,
cluster-api or cluster-agent. If the argument is missing or is anything else, ask which
component and stop.
This skill recommends and nothing else. It never creates or pushes a tag, edits a file or
dispatches a workflow. A person tags with the release-cli or release-cluster skill.
The rules are SemVer 2.0.0.
The components
| Component | Tag | Workflows | Paths |
cli | cli/v<version> | release-cli.yml, release-docker.yml | modules/cli/ modules/dashboard/ modules/shared/ dashboard-ui/ |
dashboard | dashboard/v<version> | release-docker.yml | modules/dashboard/ modules/shared/ dashboard-ui/ |
cluster-api | cluster-api/v<version> | release-docker.yml | modules/cluster-api/ modules/shared/ proto/ |
cluster-agent | cluster-agent/v<version> | release-docker.yml | crates/ proto/ |
Each component's full list, with its Dockerfile and default config, is its release-<component>
filter in .github/ci-config/path-filters.yml. Use those globs as the paths below. The CLI
embeds the Dashboard, so the Dashboard's changes are the CLI's too.
1. Find the last release
Fetch tags first, so a tag pushed from elsewhere is seen: git fetch --tags --quiet against the
remote that points to kubetail-org/kubetail. If the fetch fails, carry on with the local tags and
say so.
List the component's tags (git tag -l '<component>/v*') and take the highest by SemVer
precedence, not by date or by sort -V. Precedence (SemVer §11):
- Compare major, minor and patch as numbers.
- With those equal, a version with a prerelease sorts before the one without
(
1.0.0-rc.1<1.0.0). - Two prereleases compare identifier by identifier, split on
.. A numeric identifier compares as a number and sorts before an alphanumeric one; alphanumeric identifiers compare in ASCII order. With all shared identifiers equal, the shorter list sorts first. - Build metadata (
+…) is ignored.
Skip a tag whose version is not SemVer (step 5), and say you skipped it. If the component has no tag, say so and stop.
2. Collect the commits
git log --no-merges --format='%h%x09%s' <last-tag>..HEAD -- <paths>Read each commit's body as well (git log --format=%B -1 <sha>) for a BREAKING CHANGE: or
BREAKING-CHANGE: footer. A squash-merged PR's body may list several commits; read it whole.
If the list is empty, say there is nothing to release and stop.
3. Classify each commit
From the conventional-commit header, type(scope)!: subject:
| Header | Level |
! after the type or scope, or a breaking footer | major |
feat | minor |
fix, perf | patch |
docs, test, chore, refactor, ci, style, build | none |
A header that is not a conventional commit gets no level from its header: read its diff. A
build(deps) or fix(deps) bump counts as a patch when it changes what ships (a Go module, a
crate or an npm package the component uses), and as none when it touches only tests or tooling.
Read the diff (git show --stat <sha>, then the relevant hunks) when the type looks wrong for
the change. For example, a refactor that renames a CLI flag or a config key, a chore that
changes what a user sees, or a fix that removes a behaviour someone relied on. A commit under
modules/shared/ or proto/ counts only for the components whose code it changes. Classify by
what the change does to the component's users, and name each commit you reclassified and why.
What counts as breaking:
cli: removing or renaming a command, flag, argument or config key, changing an exit code, or changing output a script may parse.dashboard: removing or renaming a flag, environment variable or config key, or needing a permission the Helm chart's current release does not grant. Its GraphQL API serves its own UI alone; a change there is not breaking.cluster-api: the same as the Dashboard, plus removing or changing a GraphQL field that a released Dashboard orkubetail logsreads, since a cluster runs them at different versions.cluster-agent: the same as the Dashboard, plus a change to the gRPC contract inproto/that a released Cluster API cannot speak.
The release's level is the highest level among the commits. If it is none, say there is nothing to release and stop.
4. Pick the version
Let the last release be X.Y.Z, with or without a prerelease.
From a release (X.Y.Z, no prerelease):
- At
1.0.0or later: major →(X+1).0.0, minor →X.(Y+1).0, patch →X.Y.(Z+1). - Before
1.0.0: a breaking change or afeatbumps the minor,0.Y.Z→0.(Y+1).0; afixorperfbumps the patch,0.Y.(Z+1). SemVer leaves0.xunstable, and this is the convention every component keeps. Say plainly when this rule applies. - A bump resets every field below it (
0.3.4→0.4.0).
From a prerelease (X.Y.Z-<pre>): first find the version the prerelease leads to. Apply the
release's level, by the rules above, to the highest release tag of the component below X.Y.Z
(0.0.0 when there is none).
- If that gives
X.Y.Zor lower,X.Y.Zalready holds these changes. Offer both: the next prerelease ofX.Y.Z, andX.Y.Zitself. Recommend one and say why (more changes to test favours the prerelease; a fix-only run after a tested candidate favours the release). - If it gives a higher version, the changes outgrow
X.Y.Z: recommend that higher version, and offer its first prerelease (-rc.1) beside it.
The next prerelease increments the last numeric identifier: rc.1 → rc.2, beta.3 →
beta.4; one with no numeric identifier gains .1 (beta → beta.1). Recommend dot-separated
numbers (rc.1, rc.2) for a new version: rc10 sorts before rc2, since an alphanumeric
identifier compares as text.
The old form (rc1). Every prerelease tagged so far uses it (dashboard/v0.17.0-rc3). Do not
switch forms within one version: 0.17.0-rc.2 sorts before 0.17.0-rc1 (rc < rc1). The
next prerelease of a version in the old form is rc<n+1>, and the dotted form starts with the next
version. Say this when it applies.
Never recommend build metadata (+…).
5. Check the version
The version must match SemVer without build metadata, which tools/releasenotes and the
workflows' prerelease check (a - in the version) rely on:
^(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)(-[0-9A-Za-z-]+(\.[0-9A-Za-z-]+)*)?$Check too that the tag does not exist yet (git rev-parse -q --verify refs/tags/<tag> prints
nothing) and that it sorts above the last release. If any check fails, fix the recommendation
before printing it.
6. Report
Print, in this order:
- Recommended version, and the alternative when step 4 offers two.
- Last release: its tag and commit.
- Bump level: major, minor or patch, and the rule that turned it into this version
(the
0.xrule, a prerelease, or none). - Commits that drove it: each commit at the release's level as
sha subject, then a count of the lower-level and no-level commits. Name any commit reclassified from its diff. - Helm chart changes: for a cluster component, each commit whose PR says the chart needs a
new permission, Secret, port, environment variable or config key. The chart, in
kubetail-org/helm-charts, must ship it with this release. - Next step: tag it with
/release-clior/release-cluster, then write the notes with/release-notes <component> <tag>.
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.

