170 Commits (v1.15.0)

Author	SHA1	Message	Date
Tanmay Jain	17bc81ea6c	version: cut release v1.15.0	2 weeks ago
hashicorp-copywrite[bot]	6af0b29558	[COMPLIANCE] Update Copyright and License Headers	3 months ago
Anurag Sharma	c60dc95eda	prepare for dev 1.14.4 (#13531)	3 months ago
Anurag Sharma	e6f6dabce2	cut release 1.14.3 (#13520)	3 months ago
kp2099	847497f8f3	Merge pull request #13469 from hashicorp/karthik/prep_version_1.14.3 ... version prep 1.14.3	5 months ago
karthik P	d23da9806e	updating versiun + changelog	5 months ago
anshulSharma	c98a15a6b7	dev version bump (#13443)	7 months ago
anshulSharma	4ed31576eb	changelog update and patch release version changes (#13440) ... * changelog update and patch release version changes * typo fix	7 months ago
anshulSharma	1a01c0547b	change log update for packer 1.14.0 (#13436) ... * change log update for packer 1.14.0 * review suggested change * packer version change, the one to be released	7 months ago
kp2099	f829fd9669	prepare version 1.13.2-dev (#13408)	9 months ago
karthik P	232165097b	prepare version 1.13.1	9 months ago
anshulSharma	9086931f21	bump dev version (#13389) ... * bump dev version * missing changelog addition	9 months ago
anshulSharma	9b6353a04d	release version readiness (#13384) ... * release version readiness * changelog updated	9 months ago
anshulSharma	a80c83c40e	keeping the version file up to date (#13382)	9 months ago
Lucas Bajolet	361a432eac	version: bump main to 1.12.0-dev ... 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.	2 years ago
Lucas Bajolet	410e59f141	version: compute SemVer from rawVersion ... 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.	2 years ago
Lucas Bajolet	cdaad0cde2	version: up version handling code for SDK update ... 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.	2 years ago
Lucas Bajolet	f05124e2a4	version: set version to 1.11.0-dev ... Since we set the raw version string from version/VERSION now, we change its information to point to 1.11.0-dev until we're ready to release.	2 years ago
Lucas Bajolet	93bec31ec9	version: embed version/VERSION as version string ... 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.	2 years ago
Wilken Rivera	c138ce533e	Revert "Bumped product version to 1.12.0." ... This reverts commit cc22e282ac. The action successfully works now for the future release branch.	2 years ago
hc-github-team-packer	cc22e282ac	Bumped product version to 1.12.0.	2 years ago
Wilken Rivera	a118b5489e	Bumped product version to 1.11.0	2 years ago
Wilken Rivera	ebc1317307	Bumped product version to 1.11.0.	2 years ago
hashicorp-copywrite[bot]	19055df3ec	[COMPLIANCE] License changes (#12568) ... * Updating the license from MPL to Business Source License Going forward, this project will be licensed under the Business Source License v1.1. Please see our blog post for more details at https://hashi.co/bsl-blog, FAQ at https://hashi.co/license-faq, and details of the license at www.hashicorp.com/bsl. * Update copyright file headers to BUSL-1.1 --------- Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>	3 years ago
Lucas Bajolet	ac29a1366b	version: prepare for 1.10.0 releases	3 years ago
hashicorp-copywrite[bot]	b7df3ca36f	[COMPLIANCE] Add Copyright and License Headers (#12254) ... Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>	3 years ago
Wilken Rivera	b986a7c948	Bump development version to 1.9.0 ... Stable releases for 1.8.x will be made off of the release/1.8.x branch. Main will represent the next minor version. When ready for a release a new release branch will be created for the version.	3 years ago
claire labry	0d94e7d753	Introduce action-set-product-version for Packer (#12135) ... This change introduces the new actions-set-product-version, a tiny, but mighty, GitHub action that acts as a bridge between the product repo and our new CRT feature: automated version bumping. tl;dr automated version bumping has a new command (bob update version) in the bob CLI that automatically bumps the version to a new patch. This automation has been introduced to crt-workflows-common as a new workflow (with the new bob command) and handles version bumping at the end of the release pipeline (after being released to production); for example, 1.0.0→1.0.1 and 1.0.0-dev→1.0.0. Bumping the minor version (ie 1.0.x→1.1.0) is only supported manually via bob update version -bump minor, but not supported in CRT (this work is upcoming). This is made possible by adding the new event “bump-version” in the ci.hcl file in this PR. What this small action does: Allows for the static version string from the version/VERSION file to be read by the new CRT workflow and automagically be bumped to the next version (whether it be a minor, or patch, or major version bump). Outputs an error if there’s no VERSION file in the version dir Outputs an error if there’s no version string in the VERSION file Is able to parse product_version if it is 1.3.0-alpha1 as 1.3.0 (example: when product_version = 1.3.0-alpha1, base_version = 1.3.0) Is able to parse prerelease product versions such as alpha1 (example prerelease_product_version = alpha1) in the statement above.	3 years ago
Wilken Rivera	82bcc9e671	Reset to dev mode	3 years ago
Wilken Rivera	e4f31384a3	Cut release 1.8.5	3 years ago
Lucas Bajolet	83ca7c203c	prepare 1.8.5	3 years ago
Lucas Bajolet	83cc093d50	cut release 1.8.4	3 years ago
Wilken Rivera	0c9c3fe48c	Put in dev mode 1.8.4	4 years ago
Wilken Rivera	38b47d8211	Cut release 1.8.3 ... * Fix spacing in CHANGELOG * Add release date to CHANGELOG	4 years ago
Wilken Rivera	f752f8dd63	Put in dev mode	4 years ago
Wilken Rivera	f0e24a249b	Cut release v1.8.2	4 years ago
Wilken Rivera	ecacd59f0f	Put in dev mode 1.8.2 (#11822)	4 years ago
Wilken Rivera	467529f597	Cut release 1.8.1	4 years ago
Wilken Rivera	ec912cae9e	Put in dev mode	4 years ago
Wilken Rivera	70806cb27e	Bump version for 1.8.0 release	4 years ago
Michele Degges	b63a9c9803	Onboard to CRT (#11564) ... Onboard Packer to CRT Co-authored-by: Wilken Rivera <wilken@hashicorp.com> Co-authored-by: Claire Labry <claire@hashicorp.com>	4 years ago
packer-ci	f0e7edd62d	Putting source back into Dev Mode	4 years ago
packer-ci	661b85e18c	cut version 1.7.10	4 years ago
packer-ci	fd487b4d8b	Putting source back into Dev Mode	4 years ago
packer-ci	418284afee	cut version 1.7.9	4 years ago
packer-ci	9cfe02042b	Putting source back into Dev Mode	4 years ago
packer-ci	c261e9d641	cut version 1.7.8	4 years ago
packer-ci	079c0004fd	Putting source back into Dev Mode	4 years ago
packer-ci	d0c2326671	cut version 1.7.7	4 years ago
packer-ci	8eac348d97	Putting source back into Dev Mode	4 years ago