packer-plugin-veertu-anka
packer-plugin-veertu-anka copied to clipboard
Bump github.com/hashicorp/packer-plugin-sdk from 0.5.1 to 0.5.2
Bumps github.com/hashicorp/packer-plugin-sdk from 0.5.1 to 0.5.2.
Release notes
Sourced from github.com/hashicorp/packer-plugin-sdk's releases.
v0.5.2
Upgrade Notes
Upgrading to this release may fail until you've applied one of the fixes documented in packer-plugin-sdk#187. Consumers of the Packer plugin SDK require a replace directive within their plugin's go module file to point to a compatible version of go-cty. The replace directive subject to change in future releases can be applied by running the
packer-sdc fix
sub-command to apply the replace directive to your plugin with a recommended version of the go-cty fork.Plugins already working with Packer Plugin SDK v0.5.1 are advised to apply the updated SDK fixes by re-running
packer-sdc fix
against the plugin's root directory. The updated SDK fixes will bump the supported version of the go-cty fork to v1.13.3, which is required for working with hcl/v2 version 2.17.0 and above.
- Bumped github.com/zclconf/go-cty to v1.13.1: to bring in the latest supported changes of zclconf/go-cty and hashicorp/hcl/v2 to the SDK.
- Bumped github.com/hashicorp/hcl/v2 to v2.19.1: to bring in support for the latest HCL/v2 refinements builder and enhancements. Refinements are non-breaking changes but you may see some changed results in your unit test of operations involving unknown values.
- Updated
packer-sdc fix
: to upgrade the replace version for github.com/nywilken/go-cty from v1.12.1 to v1.13.3.What's Changed
Exciting New Features 🎉
- Add capability to specify additional build args to be executed when running acceptance tests against builders by
@lbajolet-hashicorp
in hashicorp/packer-plugin-sdk#202- Bump supported version of go-cty to v1.13.3 by
@nywilken
in hashicorp/packer-plugin-sdk#215Security Changes
- Bump go-getter to v2.2.1 by
@zliang-akamai
in hashicorp/packer-plugin-sdk#200- Address reported CVEs along with Go toolchain vulnerabilities by
@nywilken
in hashicorp/packer-plugin-sdk#208, hashicorp/packer-plugin-sdk#213Bug Fixes🧑🔧 🐞
- Fix issue where packer-sdc mapstructure-to-hcl was incorrectly mixing underlying structs for types with similar mapstructure tags by
@nywilken
in hashicorp/packer-plugin-sdk#212- hcl2helper: preemptively panic on nil hcl spec by
@lbajolet-hashicorp
in hashicorp/packer-plugin-sdk#204Other Changes
- packer-sdc/struct-markdown: Allow packer-internal as project directory for testing purposes by
@nywilken
in hashicorp/packer-plugin-sdk#218New Contributors
@zliang-akamai
made their first contribution in hashicorp/packer-plugin-sdk#200Full Changelog: https://github.com/hashicorp/packer-plugin-sdk/compare/v0.5.1...v0.5.2
Commits
eac3a5f
Cut release v0.5.2e599745
packer-sdc/struct-markdown: Allow packer-internal as project directory for te...4fb8273
Initial fix for underlying struct mis-match bugc170d73
Update go-cty fixer replace directive to github.com/nywilken/go-cty v1.13.3fe7beb7
Bump upstream modules to support latest hcl/v2 offerrings3327058
depg: bump golang.org/x/net to 0.17.0 for security fixes530fc82
deps: bump github.com/hashicorp/vault/api to 1.10.0 for security fixes4d8c199
deps: bump github.com/hashicorp/consul/api to v1.25.1 for security fixes9e65ca1
deps: bump github.com/hashicorp/yamux to v0.1.16961c20
deps: bump github.com/mitchellh/cli to v1.1.5 for security fix- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)