Quickly sandbox your AI agent.
Python
chore: uvr upgrade skill and workflow
Tyler Payne6d4e00cd10bf
diff --git a/.claude/skills/release/SKILL.md b/.claude/skills/release/SKILL.mdindex 8a3ab39..a9d47b2 100644--- a/.claude/skills/release/SKILL.md+++ b/.claude/skills/release/SKILL.md@@ -173,20 +173,25 @@ If something goes wrong, see `references/troubleshooting.md`.```bashgit checkout maingit pull --rebase-git merge --no-ff <release-branch> -m "Merge <release-branch>"+git fetch origin <release-branch>+git merge --no-ff origin/<release-branch> -m "Merge <release-branch>"git push```-After merging, clean up release notes:+**Why `git fetch` and `origin/<release-branch>`:** the post-release bump job runs in CI and pushes a `chore: bump to next dev versions` commit (and creates the `-base` baseline tag) on the remote release branch *after* `uvr release` returns. Your local copy of the branch does not have that commit. Merging your local tip leaves main stuck at the released version instead of the next dev version, and `uvr status` will then resolve `DIFF FROM` to the previous release tag instead of the new baseline. Fetch and merge the remote tip.++**NEVER** merge pre-release branches back to main. Stay on the branch through the pre-release cycle, then merge after the stable release.++**TAKE CARE** merging post-release branches back to main — they branch from an old tag, so pyproject.toml versions will conflict. You may need to accept main's versions or cherry-pick just the fix commits. See `references/post-releases.md`.++## 9. Finally++If packages were released successfully, clean up release notes:```bashrm -rf .uvr/release-notes/```-**DO NOT** merge pre-release branches back to main. Stay on the branch through the alpha → beta → rc → stable cycle, then merge after the stable release. See `references/pre-releases.md`.--**TAKE CARE** merging post-release branches back to main — they branch from an old tag, so pyproject.toml versions will conflict. You may need to accept main's versions or cherry-pick just the fix commits. See `references/post-releases.md`.----## Example@@ -207,6 +212,10 @@ User says: "Let's release the new changes"## References**Commands:**+<<<<<<< current+=======+- `references/cmd-version.md` — read, set, or bump package versions+>>>>>>> incoming- `references/cmd-init.md` — scaffold the release workflow- `references/cmd-validate.md` — check release.yml against schema- `references/cmd-release.md` — plan and dispatch a release (all flags)@@ -219,6 +228,5 @@ User says: "Let's release the new changes"- `references/release-plan.md` — what the release plan JSON contains- `references/custom-jobs.md` — how to add your own jobs to the workflow- `references/dev-releases.md` — publishing `.devN` versions for testing-- `references/pre-releases.md` — alpha, beta, and release candidate versions- `references/post-releases.md` — correcting an already-released version- `references/troubleshooting.md` — common problems and fixesdiff --git a/pyproject.toml b/pyproject.tomlindex 12edc96..68efd97 100644--- a/pyproject.toml+++ b/pyproject.toml@@ -18,8 +18,8 @@ default = true[tool.uvr.config]latest = "quick-sandbox"exclude = ["quicksand-gh-runners"]-workflow_version = "0.30.2a0"-skill_version = "0.27.1a3"+skill-version = "0.40.0"+workflow-version = "0.40.0"[tool.uvr.runners]quicksand-agent = [["self-hosted", "linux", "x64"], ["self-hosted", "macos", "arm64"]]