Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump github.com/hashicorp/go-getter from 0.0.0-20181213035916-be39683deade to 1.7.0 #339

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 6, 2023

Bumps github.com/hashicorp/go-getter from 0.0.0-20181213035916-be39683deade to 1.7.0.

Release notes

Sourced from github.com/hashicorp/go-getter's releases.

v1.7.0

What's Changed

New Contributors

Full Changelog: hashicorp/go-getter@v1.6.2...v1.7.0

v1.6.2

What's Changed

  • Fix no getter available for X-Terraform-Get source protocol when using bare github or bitbucket hostnames: #370

v1.6.1

No release notes provided.

v1.5.11

What's Changed

New Contributors

Full Changelog: hashicorp/go-getter@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_TOKEN environment 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 optional ref argument, and would instead only allow named refs from the remote. As a compromise, go-getter will now accept for ref anything that git checkout would accept as a valid tree selector, unless you also set depth to activate shallow clone mode in which case ref must be a named ref due to requirements of the Git protocol in that case. (#345)

v1.5.9

Fix git shallow clone (depth parameter) for any ref. See #266

v1.5.8

No release notes provided.

v1.5.7

In 1.5.7, we moved to using signore, an internal tool, for GPG signing.

v1.5.5

... (truncated)

Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will 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 labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will 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.

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 6, 2023
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/hashicorp/go-getter-1.7.0 branch 5 times, most recently from bd71be3 to 6a4effe Compare March 25, 2023 05:25
Bumps [github.com/hashicorp/go-getter](https://github.com/hashicorp/go-getter) from 0.0.0-20181213035916-be39683deade to 1.7.0.
- [Release notes](https://github.com/hashicorp/go-getter/releases)
- [Commits](https://github.com/hashicorp/go-getter/commits/v1.7.0)

---
updated-dependencies:
- dependency-name: github.com/hashicorp/go-getter
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/hashicorp/go-getter-1.7.0 branch from 6a4effe to c2d7032 Compare March 25, 2023 05:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants