qdrant-version-upgrade — GitHub Copilot skill: what it does
Provides rules for upgrading Qdrant and its SDK without downtime or data corruption. Helps plan rolling cluster upgrades and multi-version storage migrations.
npx skills add github/awesome-copilot --skill qdrant-version-upgradeWhat qdrant-version-upgrade does
The skill outlines compatibility rules between Qdrant server and its client libraries. Order matters here. You first upgrade the SDK to the next minor version, and only then update the database server. Disk storage guarantees backward compatibility for only one minor version. Because of this, moving from 1.15.x to 1.17.x requires an intermediate step on 1.16.x.
Zero-downtime rolling upgrades require a replication factor of 2 or higher. Nodes are updated one by one while the remaining instances handle incoming traffic. In Qdrant Cloud, intermediate storage migrations run automatically, and environments can be managed through the qcloud CLI.
Install this skill if you operate self-hosted Qdrant nodes and need to safeguard your index data during upgrades. If you fully rely on Qdrant Cloud, you can safely skip these manual maintenance rules.
What it helps with
- order SDK and server updates correctly
- run zero-downtime rolling upgrades on clustered nodes
- migrate storage files safely across minor releases
- manage cluster updates using the qcloud CLI tool
Example prompts for the agent
- How do I upgrade Qdrant from 1.15.x to 1.17.x without data loss?
- Show me how to run a rolling upgrade on a Qdrant cluster with replication factor 2
- Should I upgrade the Qdrant SDK or the server first?
How to install qdrant-version-upgrade
1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill qdrant-version-upgrade2GitHub CLI
gh skill install github/awesome-copilot qdrant-version-upgrade3Manually: put the files in place
.github/skills/qdrant-version-upgrade/SKILL.md1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill qdrant-version-upgrade -a claude-code2Manually: put the files in place
~/.claude/skills/qdrant-version-upgrade/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/qdrant-version-upgrade/
Manually: put the files in place
.agents/skills/qdrant-version-upgrade/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/qdrant-version-upgrade/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
Platform CLI
gemini skills install https://github.com/github/awesome-copilot --path skills/qdrant-version-upgradeManually: put the files in place
.devin/skills/qdrant-version-upgrade/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set554
The whole set →Similar
Questions about qdrant-version-upgrade
How to install qdrant-version-upgrade in GitHub Copilot?
Run gh skill install github/awesome-copilot qdrant-version-upgrade or npx skills add github/awesome-copilot --skill qdrant-version-upgrade. You can also save the file to .github/skills/qdrant-version-upgrade/SKILL.md.
What does the qdrant-version-upgrade skill do?
It gives GitHub Copilot exact version compatibility rules, safe migration sequences between Qdrant and its SDK, and requirements for zero-downtime updates.
Can I skip a minor version when upgrading self-hosted Qdrant?
No, storage compatibility is guaranteed across only one minor version step. You must upgrade sequentially, though Qdrant Cloud automates multi-version jumps directly.
Source text
SKILL.md · MIT
--- name: qdrant-version-upgrade description: "Guidance on how to upgrade your Qdrant version without interrupting the availability of your application and ensuring data integrity." --- # Qdrant Version Upgrade Qdrant has the following guarantees about version compatibility: - Major and minor versions of Qdrant and SDK are expected to match. For example, Qdrant 1.17.x is compatible with SDK 1.17.x. - Qdrant is tested for backward compatibility between minor versions. For example, Qdrant 1.17.x should be compatible with SDK 1.16.x. Qdrant server 1.16.x is also expected to be compatible with SDK 1.17.x, but only for the subset of features that were available in 1.16.x. - For migration to the next minor version, it is recommended to first upgrade the SDK to the next minor version and then upgrade the Qdrant server. - Storage compatibility is only guaranteed for one minor version. For example, data stored with Qdrant 1.16.x is expected to be compatible with Qdrant 1.17.x. If you need to migrate more than one minor version, it is required do the upgrade step by step, one minor version at a time. For example, to migrate from 1.15.x to 1.17.x, you need to first upgrade to 1.16.x and then to 1.17.x. Note: Qdrant Cloud automates this process, so you can directly upgrade from 1.15.x to 1.17.x without intermediate steps. - A Qdrant cluster with a replication factor of 2 or higher can be upgraded without downtime by performing a rolling upgrade. This means that you can upgrade one node at a time while the other nodes continue to serve requests. This allows you to maintain availability of your application during the upgrade process. More about replication factor: [Replication factor](https://search.qdrant.tech/md/documentation/operations/distributed_deployment/?s=replication-factor) For managing Qdrant version upgrades in Qdrant Cloud, you can use the [qcloud](https://github.com/qdrant/qcloud-cli) CLI tool.
© github · MIT · github/awesome-copilot