Breaking Changes

We recommend reading the release notes from the other alphas to see all the new features, and read about breaking changes that have been introduced. The data storage format for the v1 of Porter is not yet fixed. We are not providing migrations for your data between pre-release versions. We will provide migrations from the stable version of Porter (v0.38) to the new v1 format when we have a release candidate. So don't use the v1 prereleases for anything important!

What's Changed

• Update helm3 mixin doc by @MChorfa in #1749
• Properly format numbers parsed from jsonPath outputs by @carolynvs in #1755
• Use helm3 for the airgap example by @carolynvs in #1759
• Install the helm3 mixin on CI machine by @carolynvs in #1760
• Announce v1.0.0-alpha.3 by @carolynvs in #1768
• Continue installing the helm2 mixin by @carolynvs in #1774
• Remove debug print statement by @carolynvs in #1775
• Fix website typos by @carolynvs in #1776
• Use the helm3 mixin everywhere by @carolynvs in #1772
• Lock down file permissions by @carolynvs in #1770
• Make log persistence configurable by @carolynvs in #1780
• Reconcile installation upon apply by @carolynvs in #1764
• Add porter mixin create command by @joshuabezaleel in #1602
• Reduce how often we hit the database by @carolynvs in #1783
• Blog about the helm3 v0.1.14 mixin release by @carolynvs in #1777
• Fix broken links by @carolynvs in #1786
• update helm3 mixin documentation to the latest release by @MChorfa in #1788
• Add command to show historical runs of porter by @phillipahereza in #1779
• Sync operator with porter v1 by @carolynvs in #1785
• Sync main into release/v1 by @carolynvs in #1790
• Allow config env vars to be empty by @carolynvs in #1794
• Print applied file in debug mode by @carolynvs in #1796

Full Changelog: v1.0.0-alpha.3...v1.0.0-alpha.4

Install or Upgrade

We would love for you to try out v1.0.0-alpha.4 and send us any feedback that you have! Keep in mind that the v1 prerelease is not suitable for running with production workloads, and that data migrations will not be provided or supported for v1 prerelease.
The prerelease is intended for you to try out the new features in Porter, and provide feedback but won't work with existing installations.

One way to try out Porter without messing with your current installation of Porter is to install Porter into a different
PORTER_HOME directory.

MacOS

export PORTER_HOME=~/.porterv1
export VERSION="v1.0.0-alpha.4"
curl -L https://cdn.porter.sh/$VERSION/install-mac.sh | bash

Linux

export PORTER_HOME=~/.porterv1
export VERSION="v1.0.0-alpha.4"
curl -L https://cdn.porter.sh/$VERSION/install-linux.sh | bash

Windows

$PORTER_HOME="$env:USERPROFILE\.porterv1"
$VERSION="v1.0.0-alpha.4"
(New-Object System.Net.WebClient).DownloadFile("https://cdn.porter.sh/$VERSION/install-windows.ps1", "install-porter.ps1")
.\install-porter.ps1 -PORTER_HOME $PORTER_HOME

Now when you want to use the v1 version of Porter, set the PORTER_HOME environment variable and add it to your PATH.

Posix Shells

export PORTER_HOME=~/.porterv1
export PATH="$PORTER_HOME:$PATH"

PowerShell

$env:PORTER_HOME="$env:USERPROFILE\.porterv1"
$env:PATH+=";$env:PORTER_HOME"