v0.33.0

Features

• Add a short flag for --reference #1437. You can now use -r instead of --reference in commands such as porter explain -r getporter/porter-hello:v0.1.0.

Fixes

• Fix typo in StartDockerRegistry target #1427
• Fix the service fabric example bundle #1428

Misc

• Bump cnab-go to support Porter Operator #1435
• Update exec-outputs example for the k8s driver #1433

Install or Upgrade

Run (or re-run) the installation from https://porter.sh/install to get the latest version of porter.

v0.32.0

Features

• Use a custom extension for File type (#1420)

Misc

• Update contributing tutorial #1423
• Fix helm chart image on homepage #1424

Install or Upgrade

Run (or re-run) the installation from https://porter.sh/install to get the latest version of porter.

v0.31.2

Porter v0.31.2

🩹 Patch release making sure the deprecated tag field for dependency bundle declarations is still honored pre-1.0

Changeset

• fix(*): continue to support dependency tag use for time being (#1421) 7e76712

v0.31.1

Porter v0.31.1

This release is a hotfix 🔥 that adds support for the deprecated --tag flag in commands missed the first time around (porter explain, porter inspect, porter parameters and porter credentials).

Full commit list

• fix(*): no really, set reference off of deprecated tag value pls ab21a2f
• Release notes for v0.31.0 9d14ff4

v0.31.0

📬 Sign up for our mailing list for highlights of new releases, announcements of blog posts and explanations of new features and upcoming changes before they happen.

Porter v0.31.0

This release brings a whole lot of goodness, including:

• Test parallelization for remarkably faster PR feedback 🏎 💨
• Windows support++, both for Porter devs and in CI via a custom Windows agent 🆒
• Starting the exciting transition from make to Mage 🔮
• Slimming down the installer's base image (Thanks @i-am-jeetu and @wisdommatt!) 💅
• A bunch of doc improvements and clarifications ✨

For notable features, this release closes out the work we've done to improve on the CI/CD story for Porter, including support for metadata updates on applicable commands:

• At build-time, e.g. porter build --name NewName --version 0.1.1
• At time of publishing, e.g. porter publish --tag canary --registry myregistry.com/myorg

For the latter, the same previously-built bundle can be published with any number of different reference values, without the need for
rebuilding.

Breaking changes

To support the manifest and command updates mentioned above, a few breaking changes have been introduced:

• For the porter publish command, the --tag flag now overrides the last part of the bundle reference, e.g. :VERSION. (By default it is the tag is the bundle version, e.g. :v0.1.0). The new --reference flag does what --tag previously handled, that is, overriding the entire bundle reference, e.g. myregistry.com/myorg/mybundle:v0.1.0

• Similarly (not actually breaking just yet, but phasing out) the --tag flag for all bundle action commands (install, upgrade, invoke, uninstall) is now also replaced by --reference. For this release, using --tag will still work as intended, albeit with a deprecation warning. At a later date, it will be removed entirely.

Features

• Updates to publishing: flags, invocation image tagging (#1405)
• Updated references to debian:stretch with debian:stretch-slim (#1387) @i-am-jeetu
• Generate/use canonical manifest for build and publish (#1368)
• Edited template dockerfiles to use debian:stretch-slim instead of debian:stretch 7d2b02b @wisdommatt

Fixes

• Fix passing env vars to plugins 9c7825d
• Fix command driver resolution 41866bf
• Bump helm to supported version in our workshop image ecc5f6c

Docs

• Document GHCR is CNAB compatible 8969b53
• Clarify Minkube doc is for connecting not building ed99519
• Link to bundle use cases talk 67cb696
• Doc mage (#1372)
• Include PEP process in docs fee99f3
• Contrib tutorial (#1363)
• Delete instruction to use GOPATH from the CONTRIBUTING's setup tutorial (#1369) @joshuabezaleel
• docs(kind.md): revise api server comms approaches 1415ae1

Misc (Refactors, Test & CI improvements)

• Fix jsonschema not being threadsafe by using a fixed fork b436f67
• Make more tests run in parallel 0a95f45
• Recategorize test 488a832
• Capture working directory and env vars at startup 44f3b39
• Bump cnab-go to v0.15.0 (#1397)
• Stop build if we can't install a mixin f9d8d29
• Wait 3 minutes for Docker service to start ba1a809
• Fix starting docker for tests 95c45b4
• Use fmt.Println for info messages from mage 746dd08
• Set GOPATH/bin on PATH properly d295735
• Sync az mixin doc f1764f9
• fix(examples/service-fabric-cli): fix Dockerfile build (#1388)
• Make porter binary available during publish 0e0f901
• Run Smoke Tests on Windows (#1321)
• Bump cnab-go to v0.14.1 b1bcc95
• Replace stable helm charts with bitnami charts (#1365)
• Open left nav to selected page d8bb0cb
• Remove symlink from porter theme 3679f79

Install or Upgrade

Run (or re-run) the installation from https://porter.sh/install to get the latest version of porter.

v0.30.1

📬 Sign up for our mailing list for highlights of new releases, announcements of blog posts and explanations of new features and upcoming changes before they happen.

Porter v0.30.1

This corrects regressions from our last release. RIP v0.30.0 💔 It also has some prep work that will enable us to have a homebrew package (#1329). It change where files are stored in ~/.porter/, aka PORTER_HOME. This does not have any impact on commands or how to install however.

When you install v0.30.1, you will get some new directories ~/runtimes and ~/mixins/MIXIN_NAME/runtimes. If you are upgrading, it will leave a few files around that are no longer used. Feel free to delete them after upgrading:

• ~/.porter/porter-runtime
• ~/.porter/mixins/MIXIN_NAME/MIXIN_NAME-runtime e.g. ~/porter/mixins/exec/exec-runtime (this is true for all mixins, not just exec)

Additionally, if you were trying to use images in your porter.yaml, this corrects an accidental regression where images.NAME.digest was renamed to images.NAME.contentDigest. If you run into trouble, make sure you are using images.NAME.digest.

Fixes

• Revert images.contentDigest back to digest #1358
• Fix defaulting of reference on windows #1356
• Update porter-hello example to use registry #1351

Misc

• Split up PORTER_HOME #1329
• Fix mac install script #1350

v0.30.0

📬 Sign up for our mailing list for highlights of new releases, announcements of blog posts and explanations of new features and upcoming changes before they happen.

Porter v0.30.0

This release brings a ton of documentation improvements, a handful of fixes and refactors and a couple of features. As always, thank you to all of the contributors who participated in this release.

The most notable change brings a few new fields to the metadata section of the Porter manifest as well as deprecating a few. The tag field is now deprecated, both in the metadata section and also as a field on dependency listings. (Note: older manifests still using this field will still be supported for the time being, though a deprecation warning will be printed.)

In its place, the direct correlate is the reference field (again, both in the metadata section and for a dependency listing.) However, we've also introduced the registry field in the metadata section in an effort to streamline and simplify the amount of metadata needed to construct bundle and installer image references. Therefore, use of registry is recommended over the reference override.

As an example, the metadata section of the default manifest created by Porter now looks like:

name: porter-hello
version: 0.1.0
description: "An example Porter configuration"
# TODO: update the registry to your own, e.g. myregistry
registry: getporter

Porter handles the construction of the bundle and installer image references from the three name, version and registry fields. We'd then have getporter/porter-hello:v0.1.0 as the bundle reference and getporter/porter-hello-installer:v0.1.0 as the installer image reference.

These updates are part of a larger epic to support dynamically overriding these fields and thus enabling automation and CI use cases to easily build or publish a bundle on the fly with values that might differ from the defaults in the manifest itself. These CLI features are due to roll out in the next releases.

See https://porter.sh/author-bundles/#bundle-metadata for the full details on the updated fields.

Features

• Porter manifest updates (#1343)
• Ensure content digest exists for the installer image when pulling a bundle via tag (#1306)

Docs

• Move links, add project clarification (#1339 @nhcarrigan
• Improve mixin dev guide for schema command (#1330)
• Add logo page (#1319)
• Add copyright to website footer (#1325)
• Update the landing page for Porter Docs removing the porter CLI commands. (#1322) @iennae
• 🎨 Align date to left and put under title in article/blog page (#1315) @dev-drprasad
• 🐛 Fix md syntax in CONTRIBUTING.md (#1316) @dev-drprasad
• Update documentation related to registries (#1309) @MChorfa
• CNCF Announcement (#1303)
• Improve authory byline on blog posts (#1304)
• Add blog framework (#1300)
• Add GOVERNANCE file (#1284)

Fixes

• Indicate where publish failed in error message (#1338)
• fix(images): update digest field for a mapped image (#1308)
• fix custom metadata serialisation (#1295) @simongdavies

Refactors

• Refactor when parameters flags are parsed (#1337)

Install or Upgrade

Run (or re-run) the installation from https://porter.sh/install to get the latest version of porter.

v0.29.1

📬 Sign up for our mailing list for highlights of new releases, announcements of blog posts and explanations of new features and upcoming changes before they happen.

Fixes

• Update logo usage (#1299)
• Print the captured output for jsonPath outputs (#1298)
• Improve documentation preview experience (#1293)
• Add New Logo (#1294) by @flynnduism
• Add automatic DCO signoff hook (#1297)
• Update footer for CNCF transition (#1296)
• Template installation name and custom metadata (#1290)
• Add redirect links to the calendar, forum, and devstats (#1289)
• fix(publish.go): remove shadow InsecureRegistry field (#1287)
• update applicable URLs per the getporter org transition (#1275)
• Make docs preview run into docker (#1246) by @MChorfa
• don't exclude Dockerfile and .dockerignore from build context (#1263)
• docs(*): add missing colon where needed (#1283)
• update azure pipeline urls (#1277)
• Include docker mixin docs on site (#1282)
• move to Apache 2.0 per CNCF (#1278)
• chore(.github): update assign-issues action (#1271)
• chore(_redirects): update links where applicable (#1273)
• fix(schema/exec.json): add missing suppress-output entry (#1265)
• ref(Makefile.kind): bump kind and remove darwin workaround (#1269)
• docs(CONTRIBUTING.md): add DCO section (#1267)
• Adds support for debugging plugins (#1198) by @simongdavies
• docs(dependencies.md): mention ordering (#1238)

Install or Upgrade

Run (or re-run) the installation from https://porter.sh/install to get the latest version of porter.

v0.29.0

📬 Sign up for our mailing list for highlights of new releases, annoucements of blog posts and explanations of new features and upcoming changes before they happen.

Breaking Changes

This release has a breaking change to the porter.yaml file for anyone using dependencies. Look at the updated Dependencies page for more information. In summary, dependencies have changed in the yaml from a map to a list and now require a name field.

Features

• User Defined Order for dependencies (#1170) by @MChorfa
• Include dependencies in porter explain (#1236) by @MChorfa
• Move kubernetes mixin to its own repository https://github.com/deislabs/porter-kubernetes (#1245) by @MChorfa

Fixes

• Remove extra quotes around jsonpath output in kubernetes mixin (#1227)
• Add OWNERS.md file to project (#1248)
• fix(dependencies.go): verify dep match before checking params (#1242)
• fix(adapter.go): set initial sequence slice to 0 length (#1244)

Install or Upgrade

Run (or re-run) the installation from https://porter.sh/install to get the latest version of porter.

v0.28.1

Fixes

• Fix setting PORTER_HOME on plugins (Makes Porter on Windows happy again) #1235
• Link to mailing list and slack on install page #1234
• 🐛 Fix non strings yaml keys causing panic #1223
• Add migration instructions for azure plugin #1231

Install or Upgrade

Run (or re-run) the installation from https://porter.sh/install to get the latest version of porter.