* Bump version to 1.15.2 and update changelog for release
* Cleanup changelog by removing outdated entries and sensitive data ref… (#13619)
* Cleanup changelog by removing outdated entries and sensitive data references
* Clarify provisioner behavior in changelog to improve understanding of lifecycle enforcement
* Update changelog to clarify provisioner lifecycle enforcement and remove outdated bug fix entry
Co-authored-by: Copilot <[email protected]>
---------
Co-authored-by: Copilot <[email protected]>
---------
Co-authored-by: Copilot <[email protected]>
Since we released 1.11.0 today, we need to have main point to the next
minor release of Packer so CI succeeds, otherwise we get an unexpected
output for the version being out-of-date.
A bug in the SDK prevents us from calling SemVer on the PluginVersion
derived from the rawVersion, as when doing so, we reset the semVer
attribute to only use the core part of the version, thereby dropping any
information on pre-release/metadata.
This is not ideal, and arguably not wanted. So in order to not lose this
information, we re-compute the SemVer from rawVersion, this way we don't
overwrite it for both structures.
Since the SDK was updated and now accepts raw version strings in
addition to also supporting metadata officially, we can start using
those functions in our version package as well.
Since we have both version/version.go and version/VERSION to specify
version strings, both are a bit redundant.
As version/VERSION is supposed to be the source of truth now, we are
using it to derive the version informaiton we used to rely on in Packer
and its subcommands.
Note: doing this prevents us from changing the version/prerelease
through ldflags though as we derive Version/VersionPrerelease from the
rawVersion variable.
Sanya
Tanmay Jain
Hari
Anurag Sharma
kp2099
anshulSharma
Lucas Bajolet
Wilken Rivera
hc-github-team-packer