Versions
Manage connector versions — create new iterations while keeping the current one live.
Each connector can have multiple versions. Every version has its own configuration, build, and deployment state — completely independent from other versions. This lets you develop a new iteration of your connector while the current one stays live in production.
Versions use major version numbering: 1.0.0, 2.0.0, 3.0.0, and so on. In the Productsup platform, end-users see versions as suffixes on the connector name (e.g. "My Connector v1", "My Connector v2").
Creating a new version
To create a new version, use the version selector in the Dev Portal and click Add version. The new version is created by copying the most recent version:
What gets copied:
- Version name and description
- Readme
- All configuration (VCS, application, individual config, execution config, type-specific config)
- Dev environment references (account, project, site)
What starts fresh:
- Version number (incremented to the next major version)
- Build and deployment state — the new version starts in
Updatedstate, ready to build - Production environment references
Each version goes through its own deployment pipeline: build, sync to dev, test, sync to prod, release.
Working with multiple versions
Common scenarios:
- Iterating on a connector — create a new version, make changes, test on dev, then sync to prod. The old version stays live until the new one is synced.
- Supporting multiple integrations — maintain separate versions with different configurations for different use cases.
- Rolling back — if a new version has issues, the previous version's production deployment remains intact. You can re-sync the older version to restore it.
Each version has independent dev and prod environments. Syncing version 2 to production does not affect version 1's production deployment — both can coexist.
Deleting a version
Versions can be deleted if they are not in use on the platform — meaning no active datasource, export, or data service on the Productsup platform references them.
Deletion is a two-step process:
- Move to bin — soft-deletes the version. It can be restored from the connector bin.
- Permanent delete — removes the version, its Docker image, and all platform references. This is irreversible.
You cannot delete a version that is actively assigned to sites on the Productsup platform. Remove the assignment first, then delete.
How is this guide?