Skip to main content
A package is a versioned snapshot of your entire component library. When you publish a package, Metabind freezes all your components at that moment — the code, properties, and assets. Content types reference specific package versions, ensuring your content always renders consistently.

​
Publish a package

  1. Navigate to Components and click Packages in the header
  2. Click Create
  3. Enter a version number (e.g., 1.0.0)
  4. Add an optional description
  5. Click Publish Package
The package is created immediately. There’s no draft state — packages are published the moment you create them.

​
Versioning

Packages use semantic versioning: MAJOR.MINOR.PATCH
  • 1.0.0 → 1.0.1 for small fixes
  • 1.0.0 → 1.1.0 for new features
  • 1.0.0 → 2.0.0 for breaking changes
Each version must be unique and higher than the previous. You can’t overwrite or go backwards.

​
What’s included

A package captures:
  • All components in your project
  • Component code and compiled output
  • Assets used by components
  • Dependencies on other packages

​
Packages are immutable

Once published, a package never changes. This is intentional — it guarantees that content using version 1.0.0 always renders the same way, even months later. To make changes, publish a new version. Then update your content types to use the new version when you’re ready.

​
What’s next

Versioning

Understand how packages, content types, and content versions work together.

Content Types

Connect packages to content types.