Releases: hashicorp/go-getter
Releases · hashicorp/go-getter
v2.1.1
What's Changed
- Add Timeout to SmbClientGetter to go-getter/v2 by @nywilken in #369
- Upgrade AWS SDK version by @kmoe in #385
Other Changes
- Fix Go Tests for V2 by @claire-labry in #392
- Migrate go-getter v2 to GHA by @claire-labry in #388
New Contributors
Full Changelog: v2.1.0...v2.1.1
v1.6.2
v2.1.0
v1.6.1
Merge pull request #362 from hashicorp/update-x/sys-for-go1.18 Update `golang.org/x/sys` to work with `go1.18`
v2.0.2
v2.0.1
Enhancements
- Append tar and ova decompressor in v2 by @LeConTesteur in #351
Bug fixes 🐞
- fixes #320: Pass context to NewRequestWithContext so HTTP requests can… by @zeisss in #324
- Ignore comments in checksum files by @azr in #350
New Contributors
- @LeConTesteur made their first contribution in #351
Full Changelog: v2.0.0...v2.0.1
v1.5.11
What's Changed
- Redact SSH key from URL query parameter by @macedogm in #348
- gcs: only run oauth test if env var is set by @schmichael in #349
New Contributors
Full Changelog: v1.5.10...v1.5.11
v1.5.10
- When fetching files from Google Cloud Storage, go-getter will now consider the
GOOGLE_OAUTH_ACCESS_TOKENenvironment variable as a potential source of a Google Cloud Platform access token. (#302) - Fixed a regression from v1.5.9 where
git::sources would no longer accept direct commit ids in the optionalrefargument, and would instead only allow named refs from the remote. As a compromise, go-getter will now accept forrefanything thatgit checkoutwould accept as a valid tree selector, unless you also setdepthto activate shallow clone mode in which caserefmust be a named ref due to requirements of the Git protocol in that case. (#345)
v1.5.9
v1.5.8
Merge pull request #336 from hashicorp/go1.14-compat Add port of url.Redact to satisfy go1.14 compatibility