vagrant
vagrant copied to clipboard
Bump github.com/hashicorp/go-getter from 1.5.9 to 1.6.1
Bumps github.com/hashicorp/go-getter from 1.5.9 to 1.6.1.
Release notes
Sourced from github.com/hashicorp/go-getter's releases.
v1.6.1
No release notes provided.
v1.5.11
What's Changed
- Redact SSH key from URL query parameter by
@macedogmin hashicorp/go-getter#348- gcs: only run oauth test if env var is set by
@schmichaelin hashicorp/go-getter#349New Contributors
@macedogmmade their first contribution in hashicorp/go-getter#348Full Changelog: https://github.com/hashicorp/go-getter/compare/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)
Commits
f710948Merge pull request #362 from hashicorp/update-x/sys-for-go1.18226a8c5Updategolang.org/x/systo work withgo1.180181334Add apt-get update before installing dependencies (#360)a2ebce9Multiple fixes for go-getter (#359)4553965fix(decompresser_zip): fix panic when decompressing protected zip file (#343)...b1336deMerge pull request #349 from hashicorp/b-gcs-testca38515gcs: only run oauth test if env var is setf5cbbb4Merge pull request #348 from macedogm/sshkey-redact17af21eRedact SSH key from URL query parameter36b68b2Redact SSH key from URL query parameter- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.
Superseded by #13119.