github getporter/porter v0.31.0

latest releases: latest, canary, v1.2.0...
3 years ago

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

Don't miss a new porter release

NewReleases is sending notifications on new releases.