Every application (web, worker, or job) that is deployed on Porter is deployed from a specific template version. This template generates the configuration required to run your application. You are given the option to select the version when you are launching the template:
If you’re not sure which version to launch, the latest version (selected by default) should be deployed.
After deploying the template, you will be notified if a chart upgrade is available:
After clicking on this button, a popup will appear detailed if there are any backwards-incompatible changes in this upgrade. If there are breaking changes, you will be given the option to configure your application.
This upgrade will be of three different types, following semantic versioning guidelines:
- Patch upgrade (ex.
v0.20.0 -> v0.20.1): upgrades with backwards-compatible bug fixes. These upgrades will not require any configuration changes: you will simply be asked to upgrade the chart, and the upgrade will occur after confirmation.
- Minor upgrade (ex.
v0.20.0 -> v0.21.0): new features with backwards-compatible configuration. These upgrades will not require any configuration changes: you will simply be asked to upgrade the chart, and the upgrade will occur after confirmation.
- Major upgrade (ex.
v0.20.0 -> v1.0.0): substantial new feature sets that may require configuration changes. These upgrades will link to docs describing the upgrade process: we will try our best to make all major upgrades as backwards-compatible as possible, with any backwards incompatibilities documented clearly.
If an upgrade causes unexpected behavior or introduces a bug, you will be able to revert this upgrade immediately from the Porter dashboard. You can do this by clicking into the chart, expanding the list of revisions, and clicking on the “Revert” button to roll back the version: