Publishing projects
When your project is ready, you publish it to make it available as a skill. You publish a specific version of a project.
Publishing projects is a two-step process:
- Create a version of your project. A version is a snapshot of a project and is associated with a specific set of shared changes. It represents a point-in-time of the project and, therefore, cannot be changed.
- Publish the version of the project that you created.
When a new version of a project is published, this version replaces the previously published version in IBM watsonx Orchestrate. IBM watsonx Orchestrate supports only one version at a time. When you publish or republish an earlier version of a project, it replaces the existing published version of the project in IBM watsonx Orchestrate.
Creating versions
Each version name must be unique. It is recommended to use the following semantic version format:
[major].[minor].[patch]-[pre-release]+[build metadata]
For example:
- Version
2.2.1
is more recent than version2.2.0
- Version
2.3.0
is more recent than version2.2.1
- Version
3.0.0
is more recent than version2.3.0
To create a version:
- Open the History tab.
- Click Version + next to the change set you want to create a version of.
Note: If you want to create a version that contains your latest changes, start by sharing your changes with your collaborators. See Sharing changes.
- Enter a name for the version and click Create.
Publishing
To publish a project:
- Open the Publish tab.
- Expand the version that you want to publish.
- Click Publish.
What to do next
When a project is successfully published, you can use it as a skill:
- Find the published project in the Skills and apps page.
- Enhance and publish the project to the skill catalog.
- Add the required project to your skill set to start using it.
You can also reuse the project in workflows.
Parent topic: