React
Harmony
NodeJS
Angular
VueA Bit component has its own version history. This history contains regular recording of changes ("snaps"), as well as tagged versions that represent a release ("tags").
Run the following to verify no issues are preventing your components to be versioned:
$bit status 
The output indicates not issues are found. It lists the modified components and their dependents. These components are ready to be versioned.
modified components
> entities/blog-post ... ok
components pending to be tagged automatically (when their dependencies are tagged)
> my-account.blog/pages/blog-page ... ok
> my-account.blog/apps/public-blog-app ... ok
> entities/blog-post ... ok
components pending to be tagged automatically (when their dependencies are tagged)
> my-account.blog/pages/blog-page ... ok
> my-account.blog/apps/public-blog-app ... ok
Run the following to version your components with a release tag:
$bit tag --message "my release message"
See command synopsis
Or use --soft if you plan on releasing components with your own CI.
The output lists the versioned components with their new release tags:
3 component(s) tagged
> my-account.my-scope/entities/blog-post@0.0.2
> my-account.blog/pages/blog-page@0.0.5
> my-account.blog/apps/public-blog-app@1.0.2
> my-account.my-scope/entities/blog-post@0.0.2
> my-account.blog/pages/blog-page@0.0.5
> my-account.blog/apps/public-blog-app@1.0.2
You may want to store your component changes or share progress with your team, without creating a release version. To do so, run the following:
$bit snap --message "my snap message"
See command synopsis
