Hello Packer Community,
The Packer team is excited to announce the release of Packer 1.10.1. This release contains enhancements for publishing built artifacts to the HCP Packer registry, security updates to address reported CVEs with the Go tooling, and a deprecation notice for mono-component plugins in Packer. For a complete list of changes, you can refer to the CHANGELOG <https://github.com/hashicorp/packer/blob/main/CHANGELOG.md#1101-january-30-2024> . Notable Changes: HCP Packer Nomenclature: The HCP Packer registry API now follows an artifact-agnostic approach for publishing and consuming built artifacts. To best support the new approach, HCP Packer components within Packer 1.10.1 will now use updated nomenclature when publishing, including two new HCP Packer data source components for consuming HCP Packer stored artifacts. The data source components hcp-packer-version <https://developer.hashicorp.com/packer/docs/datasources/hcp/hcp-packer-version> and hcp-packer-artifact <https://developer.hashicorp.com/packer/docs/datasources/hcp/hcp-packer-artifact> respectively replace, the now deprecated, hcp-packer-iteration <https://developer.hashicorp.com/packer/docs/datasources/hcp/hcp-packer-iteration> and hcp-packer-image <https://developer.hashicorp.com/packer/docs/datasources/hcp/hcp-packer-image> component data sources. The added changes are fully compatible with all existing HCP Packer workflows and do not warrant any immediate template changes by the user. However, we encourage all HCP Packer users to visit the updated HCP Packer CHANGELOG <https://developer.hashicorp.com/hcp/docs/changelog> to familiarize themselves with the nomenclature changes. Mono-component plugin deprecation: Historically, Packer has supported the loading of mono-component plugins such as packer-builder-happy-cloud or packer-provisioner-comment. With the release of Packer 1.7.0, we introduced a multi-component plugin framework, which allowed plugin developers to consolidate components into a single namespace for supporting various component types. As we continue our journey to streamline the plugin framework and enhance our tooling for managing plugins, we will remove support for mono-components in Packer 1.11.0. This deprecation is merely a notice that we will no longer support mono-components in future releases and encourage all plugin developers to move to the multi-component framework, documented with working examples at the Developing Packer Plugins <https://developer.hashicorp.com/packer/docs/plugins/creation> and Packer Plugin Scaffolding <https://github.com/hashicorp/packer-plugin-scaffolding> pages. As always, thank you for your continued support and contributions. The Packer Team -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/cc50b010-b882-41a9-bc68-371760f55a38n%40googlegroups.com.
