Step through versioning, tagging, and verification
63
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.opencode/skills/release/SKILL.mdConfirm the repo is on main and clean. Keep changes aligned with OpenCode primitives like .opencode, opencode.json, skills, and plugins when relevant.
Update versions in packages/app/package.json, packages/desktop/package.json, packages/orchestrator/package.json (publishes as ipollowork-orchestrator), packages/desktop/src-tauri/tauri.conf.json, and packages/desktop/src-tauri/Cargo.toml. Use one of these commands.
pnpm bump:patch
pnpm bump:minor
pnpm bump:major
pnpm bump:set -- 0.1.21Merge the version bump into main. Make sure no secrets or credentials are committed.
Create and push the tag to trigger the Release App workflow.
git tag vX.Y.Z
git push origin vX.Y.ZIf a tag needs a rerun, dispatch the workflow.
gh workflow run "Release App" --repo Devin-AXIS/iPolloWork -f tag=vX.Y.ZConfirm the run and the published release.
gh run list --repo Devin-AXIS/iPolloWork --workflow "Release App" --limit 5
gh release view vX.Y.Z --repo Devin-AXIS/iPolloWorkbd5caef
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.