v0.22.0

What's Changed

• Upgrade go-jsonnet to v0.17.0 by @mkmik in #299

Full Changelog: v0.21.0...v0.22.0

v0.21.0

kubecfg now returns an error if the input resource set contains multiple resources with the same version/kind/namespace/name (#258)

v0.20.0

Add support for kubectl diff --diff-strategy last-applied

v0.19.1

Fix #301 "unable map ordering with alphanumerical key"

v0.19.0

bump to go-jsonnet v0.16.0 after accidentally reverting back to go-jsonnet v0.15.0 in #292 (released in kubecfg v0.18.0).

Bumping to v0.16.0 instead of directly to v0.17.0 because some users reported a backward compat breakage in go-jsonnet 0.17.0, so giving them a chance to run v0.16.0 for a bit but with the improved kube-api clients that came with kubecfg v0.18.0

v0.18.0

bumped k8s libs to 1.19

accidentally bumped back go-jsonnet to 0.15 (See #292)

v0.17.0

bumped go-jsonnet to v0.17.0

v0.16.0

Bumped K8s client to v1.17.x

v0.15.3

upgrade to https://github.com/genuinetools/reg@v0.16.1 which is used by the resolveImage jsonnet native function.

The upgrade of this dependency should not have any functional change but should have fixed a go-gettability issue of kubecfg under go 1.14.x (see #285)

v0.15.2

(bad release, please ignore)