search

veertuinc / packer-plugin-veertu-anka

🚛 A packer plugin for Veertu's Anka Build Cloud & Anka Virtualization software which allows you to run single-use macOS VMs like you would with docker.
https://veertu.com
MIT License
69 stars 16 forks source link

Bump github.com/hashicorp/packer-plugin-sdk from 0.5.1 to 0.5.3 #170

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps github.com/hashicorp/packer-plugin-sdk from 0.5.1 to 0.5.3.

Release notes

Sourced from github.com/hashicorp/packer-plugin-sdk's releases.

v0.5.3

Upgrade notes

Upgrading to this release may fail until you've applied one of the fixes documented in hashicorp/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.2 are advised to apply the updated SDK fixes by re-running packer-sdc fix against the plugin's root directory.

What's Changed

Exciting New Features 🎉

Other Changes

Full Changelog: https://github.com/hashicorp/packer-plugin-sdk/compare/v0.5.2...v0.5.3

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 🎉

Security Changes

Bug Fixes🧑‍🔧 🐞

Other Changes

New Contributors

Full Changelog: https://github.com/hashicorp/packer-plugin-sdk/compare/v0.5.1...v0.5.2

... (truncated)

Commits
  • 38ffab0 version: cut release v0.5.3
  • 92242be version: limit core version to 3 segments
  • ddbda65 version: adapt FormatedVersion to use String
  • 2a28d48 version: introduce metadata to PluginVersion
  • b33ea9e version: add testing for version creation
  • d970fb9 Ui: add format-string alternatives to functions
  • f9edec7 Bump golang.org/x/crypto to address CVE-2023-48795
  • 4362ef5 Prepare for v0.5.3 dev
  • eac3a5f Cut release v0.5.2
  • e599745 packer-sdc/struct-markdown: Allow packer-internal as project directory for te...
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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)
dependabot[bot] commented 4 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.