Library Versioning

Marketplaces bring a host a new challenges to Code Component libraries.

• Knowing what version of the library you have, and whether there exists a newer version

• Updating to that newer version

• Reverting to an older version, if there is a breaking change that affects your project

• Installing a special dev build of a library, for special features

  • Or to support developer integration testing

Goals

We aim to resolve all of these challenges through some careful engineering and best practices.

• Current Library Version will always be displayed in the Library name

• SCM allows you to install the current release, or any prior release

• Updates are never automatic

• Notification of updates is done ( msot likely ) via email list

Future

• We may be able to audit your workspaces through the Webflow API- to check the versions of exsiting components

  • Webflow's Data API currently does not surface Code Component install data