search

vultr / packer-plugin-vultr

Packer Builder plugin for Vultr snapshots
Mozilla Public License 2.0
48 stars 20 forks source link

Bump github.com/hashicorp/packer-plugin-sdk from 0.4.0 to 0.5.1 #251

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

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

Release notes

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

v0.5.1

Upgrade Notes

This release is a fast follow to v0.5.0, which broke the installation of the packer-sdc command due to an invalid go.mod file. The v0.5.0 release has been retracted and should not be used. Consumers of the Packer Plugin SDK should update to v0.5.1. Upgrading to this release will fail until you've applied one of the fixes documneted in packer-plugin-sdk#187. We ask that you carefully review this section for details on the released changes.

  • Retracted v0.5.0: the v0.5.0 SDK release was broken because of the replace statement for go-cty. #199
  • Gob supported compile time check: we added a Go compile time check to the SDK for validating that a plugins' version of github.com/zclconf/go-cty contains encoding/gob support for cty.Type and cty.Value. #189
  • Bumped the github.com/zclconf/go-cty to v1.12.1: to bring in the latest supported changes of zclconf/go-cty and hashicorp/hcl/v2 to the SDK. Consumers of the Packer plugin SDK now require a replace directive within their plugin's go module file to point to a compatible version of go-cty. The packer-sdc command has been updated to help apply these types of fixes. #197
  • Added a fix command to packer-sdc: to help with the manual intervention and future changes to the SDK, we've introduced a fix sub-command to apply the replace directive to your plugin with a recommended version of the go-cty fork. #190, #198

What's Changed

Bug fixes🧑‍🔧 🐞

Other Changes

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

v0.5.0

Advisory ⚠️

This release breaks the installation of the packer-sdc command using go install github.com/hashicorp/packer-plugin-sdk/cmd/packer-sdc@v0.5.0. Please hold-off upgrading for now, as we work on a fix for this issue and re-release the SDK.

Apologies for the inconvenience.

Upgrade Notes

This release contains changes to the API that introduce compatibility constraints for zclconf/go-cty. Namely, the bundled version of go-cty used by the SDK is now provided via a fork to resolve the encoding/gob incompatibility issue introduced by the breaking change in zclconf/go-cty v1.11.0. Before upgrading we ask that you carefully review this section and refer to packer-plugin-sdk#187 for details on upgrading your plugin dependencies.

  • Gob supported compile time check: we added a Go compile time check to the SDK for validating that a plugins' version of github.com/zclconf/go-cty contains encoding/gob support for cty.Type and cty.Value. GH-189
  • Replaced github.com/zclconf/go-cty with a temporary fork: to avoid introducing a major breaking change to the plugin API, we've created a temporary fork of github.com/zclconf/go-cty containing support for gob encoding to use in place of the upstream go-cty package. Consumers of the Packer plugin SDK now require a replace directive within their plugin's go module file to point to a compatible version of go-cty. The packer-sdc command has been updated to help apply these types of fixes. GH-189
  • Added a fix command to packer-sdc: to help with the manual intervention and future changes to the SDK, we've introduced a fix sub-command to apply the replace directive to your plugin with a recommended version of the fork. GH-190

What's Changed

Breaking Changes 🛠

Exciting New Features 🎉

Bug fixes🧑‍🔧 🐞

Doc improvements 📚

... (truncated)

Commits
  • 3a3e3a1 Cut release v0.5.1
  • b74d508 workflows: improve replace check in go.mod
  • 4c19df0 go.mod: retract v0.5.0
  • 9be5b0f Bump Go module minimum version to 1.19
  • 04cbbf4 Add matrix builds for supported Go versions
  • 28a0063 Remove use of Go 1.20 language features
  • 5c50987 go.mod: separate go-cty out of require block
  • 57c8858 workflows: ensure we dont commit replace in go.mod
  • d758176 workflows: add packer-sdc fix to the test workflow
  • 98985e1 README: add note on local testing
  • Additional commits viewable in compare view


Dependabot compatibility score

You can trigger a rebase of this PR 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 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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

optik-aper commented 1 year ago

Superseded by #263

dependabot[bot] commented 1 year 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.