Menu
How automated publishing works in kuskus
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
How to bump package versions in kuskus — required before merging any PR that touches a package
How to update SHA-pinned GitHub Actions in kuskus workflows
Opening and reviewing PRs in the kuskus repo
Master branch protection rules, bypass policy, and how to modify when needed
Triage and label issues in the kuskus repo
Rules for safe development on this live, published extension
| name | Kuskus-Release-Process |
| description | How automated publishing works in kuskus |
Every merge to master that touches an extension's directory triggers its publish workflow:
| Extension | Workflow | Trigger path |
|---|---|---|
| Kusto Language Server | kusto-language-server-publish.yml | kusto-language-server/** |
| Kusto Syntax Highlighting | kusto-syntax-highlighting-publish.yml | kusto-syntax-highlighting/** |
| Kusto Color Themes | kusto-color-themes-publish.yml | kusto-color-themes/** |
| Kuskus Extensions Pack | kusto-extensions-pack-publish.yml | kusto-extensions-pack/** |
Pipeline: checkout → (npm ci for LS/syntax-highlighting) → bump version (phips28) → publish (HaaLeo) → push bump commit (pull-rebase-then-push, retries 5x)
Version bump commit message: 'CI: version bump [skip ci]'
| Secret | Used by |
|---|---|
VS_MARKETPLACE_TOKEN | HaaLeo/publish-vscode-extension |
TOKEN_GITHUB | phips28/gh-action-bump-version (needs push to master) |
Check the Actions tab: gh run list --workflow kusto-language-server-publish.yml --repo rosshamish/kuskus
Do not attempt to fix by running vsce publish manually.
