📬 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.