skills.rest
Fu-Jie
Fu-JieCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

publish-no-version-bump

Commit and push GitHub changes and publish to the OpenWebUI marketplace without a version bump.

286|24|Updated Dec 20, 2025
Search Tags:#automation#git#workflow#publish#marketplace#conventional-commits
One-click install
npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill publish-no-version-bump
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish-no-version-bump
Source: https://github.com/Fu-Jie/openwebui-extensions/tree/main/.github/skills/publish-no-version-bump
Command: npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill publish-no-version-bump

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Commit and push code changes to the GitHub repository and publish to the OpenWebUI official marketplace without incrementing the plugin version, reducing manual steps and the risk of accidental releases.

Core Features & Use Cases

  • Automates staging, committing, and pushing changes to the remote repository.
  • Publishes updates to the official marketplace without a version bump for non-breaking fixes and optimizations.
  • Enforces conventional commits and executes the marketplace publish script to maintain release flow.

Quick Start

Push your staged changes and publish to the OpenWebUI marketplace without updating the version.

Frequently Asked Questions about publish-no-version-bump

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish changes to the OpenWebUI marketplace without a version bump?▼

You can publish changes without a version bump by staging and pushing commits to the main branch, then running the marketplace publish script with the --force flag to update the marketplace listing without incrementing the plugin version.

When should I publish updates without increasing the plugin version?▼

Publish without a version bump for non-breaking updates such as bug fixes, performance improvements, or documentation tweaks where user-facing behavior remains the same and a full release is unnecessary.

What is the best way to automate git commits and marketplace publishing for minor fixes?▼

Automate git commits and marketplace publishing by using a script that stages changes, enforces conventional commit messages, pushes to the remote repository, and triggers the marketplace publish script with the --force flag.

Do I need conventional commits to push changes without a version update?▼

Yes, conventional commits are required when pushing changes without a version update, as the workflow enforces conventional commit standards to maintain the release flow and accurately categorize non-breaking updates.

Can I use the no-version-bump publish workflow for breaking changes?▼

No, this workflow is designed exclusively for non-breaking updates like bug fixes and documentation tweaks; breaking changes require a standard version increment to properly signal user-facing behavior modifications.

Related Skills

Explore More Software Engineering Skills→
LiozShorLiozShor
2

git-ship

Validate Git branches, diffs, and commit messages before pushing or merging.

Community
Advanced
mattbobambrosemattbobambrose
1

version-bump

Detect changed plugins from git diffs and update version fields in plugin.json and marketplace.json.

Community
Intermediate
bdsqqqbdsqqq
59

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

Community
Intermediate
jim60105jim60105
21

update-github-actions-version

Update major GitHub Actions versions in workflow files and flag breaking changes.

Community
Intermediate