Publish Command

Once you've recorded and generated assets locally, use the publish command to upload them to your storage provider.

Basic Usage

poliage publish

What It Does

1. Scans the .poliage/output directory for generated assets
2. Uploads new or changed assets to your configured storage provider
3. Commits metadata (scenario names, variants, git hash) to the platform or manifest
4. Updates the review queue (if using Poliage Platform)

Options

Examples

Dry Run

See what would be published without actually uploading:

poliage publish --dry-run

With Commit Message

poliage publish -m "Updated login screenshots for new design"

With Version Tag (for Versioned Docs)

Create a pinned version that can be referenced in versioned documentation:

poliage publish --tag v1.2

This creates pinned URLs: cdn.poliage.com/assets/{key}?tag=v1.2

Force (Skip Prompts)

poliage publish --force

Output

After publishing, you'll see a summary:

📦 Publishing assets...
 
  ✓ homepage.png (new)
  ✓ login-form.png (changed)
  ○ settings.png (unchanged, skipped)
 
Published 2 assets to Poliage Platform
Commit: abc123def

What Happens Next

Platform Mode

After publishing, assets enter the review queue in the Poliage Platform:

• Assets enter the Review Queue
• Team members can approve/reject changes
• Once approved, CDN URLs update automatically

BYOS Mode

• Assets are uploaded directly to your storage
• A manifest file is updated with new URLs
• URLs are immediately available