Publishing an Applet

an applet can be published to the turbine library as content that can be shared across your turbine account the publishing process includes publish as new content (v1) publish as a new version of existing content (v1+) (including handling merge conflicts if a remote repository has been configured) publish as new content (v1) this process applies when the applet is being published for the first time steps open the applet settings menu and select publish applet in the publish content window select publish as new content (v1) provide a name and description for the content click next select content to publish all the applet components (workspaces, playbooks, reports, etc ) will be listed check the components to be included in the package click next review content review the selected content and check for potential issues if everything looks good, click next summary confirm the details version (1 0 0), content name, description, and publish message click publish success a success message confirms that the applet has been published as new content the new content is now available in the content library publish as a new version of existing content (v1+) this scenario applies when you need to update an already published applet package steps follow steps 1–3 as in the process n the publish content window select publish as a new version of existing content (v1+) from the list, choose the package you want to update click next select content to publish review changes you can see list of dependent entities related to this component, such as assets, connectors, other referenced components all the playbook components are listed you can select to publish all related entities to this component, or select individual entities to publish once you've made your selection, click next review changes review the selected content and check for potential issues click next publish content summary add the correct confirm the new version number for this update user can indicate whether this update is a major/minor/patch in semver format (for example, 3 0 0 > 4 0 0) edit the default publish message to provide more details related to this new version update (we show a generic default message here) provide a detailed publish message (what was changed and why) click publish merge conflicts (if applicable) merge conflicts may occur if a remote repository has been configured to sync with the content in your turbine library if conflicts are detected between the local changes and the remote repository, a merge conflicts screen appears you have two options keep library changes (retains local changes) keep remote changes (keeps remote repository changes) click apply to resolve conflicts success the updated content is now published, and a confirmation message appears you can navigate to the user content library to verify the applet package has been published