Publishing Bundles

Publish your bundle to the registry so others can install it with a single command.

Prerequisites

An authenticated musher CLI (set up credentials)
A validated bundle (create one first)

Publish Your First Version

Run publish

From your bundle directory, run:

bash

musher publish

Confirm the result

On success, you'll see the published version and its OCI reference:

Output

✓ Bundle validated
✓ Published acme/code-review-kit:1.0.0
  OCI ref: registry.musher.dev/acme/code-review-kit:1.0.0

Verify as a consumer

Anyone with access can now install your bundle:

bash

mush bundle install acme/code-review-kit

Updating Your Bundle

To release a new version, edit your assets and bump the version in musher.yaml:

Make your changes

Edit, add, or remove asset files as needed.

Bump the version

musher.yaml

# Before
version: 1.0.0

# After
version: 1.1.0

Validate and publish

bash

musher validate && musher publish

Yanking a Version

Yanking soft-withdraws a version from resolution. Consumers who haven't installed it yet won't receive it, but existing installations are unaffected.

When to yank

A security issue was found in the content
The version contains broken or incorrect guidance
You accidentally published before the content was ready

Yank a version

bash

musher yank acme/code-review-kit:1.0.0

What yanking does

The version is excluded from resolution — new installs won't receive it
The version remains visible in detail views for audit purposes
Existing installations are not removed from consumer machines

Restore a yanked version

If you yanked by mistake, you can restore the version:

bash

musher unyank acme/code-review-kit:1.0.0

Visibility

Private bundles are visible only to members of your organization.
Public bundles are visible to all Musher users and appear in search results.

You can change a bundle's visibility in the Musher Console under your bundle's settings. Visibility applies to all versions of the bundle. Learn more about public discovery in Discovery & the Hub.

Troubleshooting

Error	Cause	Fix
Version already exists	You've already published this version string	Bump the `version` in `musher.yaml`
Bundle is empty	No assets defined or all source files are missing	Add at least one asset to your `musher.yaml`
Authentication failed	Credentials are expired or invalid	Run `musher login` again
Registry unavailable	The OCI registry is temporarily unreachable	Wait a moment and retry, or run `musher doctor` to diagnose

Next Steps

CI/CD Integration

Automate bundle publishing in your pipeline

Publishing Reference

Manifest schema, version states, and OCI details

Musher Commands

Complete CLI command reference

Discovery & the Hub

Make your bundle publicly discoverable