collabase-plug builds the package and uploads it. This page covers the checks, the upload and what happens to flows when you upload a new version.
Commands
The package contains one file with your code and everything it imports, a manifest and a list of the licences of the bundled dependencies.
Licences
Collabase is proprietary software and ships to customers, so it may only redistribute dependencies with a licence from the allow list. The build stops when a bundled dependency has another licence. The allow list isMIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, 0BSD, BlueOak-1.0.0, CC0-1.0, Unlicense, Python-2.0, MIT-0 and Zlib. The instance checks the list again on upload and refuses a package with another licence.
Upload
An upload needs an API token of a system administrator with the write level for Automation, created under Profile, Security. The token acts as that person. Run:- refuses a package over 20 MB,
- checks the licence list and the package in the sandbox,
- installs it as the active version of its name with the origin Own,
- writes an audit entry with the name, the version and the checksum of the package, never its content.
Names
The name of a plug is thename in package.json. It must not equal the name of a plug in the catalog or of a plug that comes with Collabase, so choose a prefix of your company. The upload is refused otherwise.
Versions
Set theversion in package.json to a new exact version for every upload, such as 0.2.0.
- The newest upload becomes the active version, and the earlier one stays installed but inactive.
- A published flow keeps using the version it was published with until you publish the flow again. Uploading a new version never changes a running flow by itself.
- When you publish a flow again, it picks up the active version. If the actions or inputs changed, the editor marks the steps that no longer fit.
- Do not rename an action or an input that flows already use. Add a new one and keep the old one until the flows have moved.