bump-version Skill
Bump WebUI to an input release version, run the full gate, and prepare a release PR with bucketed changes since the previous v-prefixed tag. Published by microsoft in webui.
Decision snapshot
Is this a fit?
Developers using webui, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is bump-version Skill?
Bump WebUI to an input release version, run the full gate, and prepare a release PR with bucketed changes since the previous v-prefixed tag. Published by microsoft in webui. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using webui
Declared skill metadata
- Source file: .github/skills/bump-version/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use bump-version Skill
- Use it for developers using webui.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/webui
- Skill file: .github/skills/bump-version/SKILL.md
What it does
Bump WebUI to an input release version, run the full gate, and prepare a release PR with bucketed changes since the previous v-prefixed tag.
Skill instructions
Bump Version Release PR Use this skill when preparing a WebUI release version bump PR. Inputs Ask for the release version if the user did not provide one. The input must be the bare semver version, without a leading v: text 0.0.16 Use v<version only when comparing or creating Git tags. Hotfix releases use the repository hotfix command instead of the stable release PR workflow: bash cargo xtask hotfix <commit <oldest-tag [--dry-run] [--support-commit <commit] <oldest-tag may be written with or without the leading v. The command increments the -hotfix.<number suffix independently for every stable release tag in range, creates each branch as hotfix/v<version, and pushes it to queue the guarded Azure release pipeline. Run with --dry-run first when preparing more than one release line. Use --support-commit when an older release line needs a newer revision of the hotfix tooling than the commit that originally introduced it. Workflow 1. Make sure the working branch is not main. If needed, cre
Verified compatibility and discovery
Frequently asked questions
What is bump-version?
bump-version is a open-source AI agent skill with Copy skill directory. Bump WebUI to an input release version, run the full gate, and prepare a release PR with bucketed changes since the previous v-prefixed tag.
Who is bump-version best for?
bump-version is best for reusing agent instructions, scripts, and references.
How do I install bump-version?
Install or run bump-version using Copy skill directory. Check bump-version for the latest setup command.
Is bump-version actively maintained?
bump-version may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
