Update google-cloud-env requirement from ~> 1.2 to >= 1.2, < 3.0

dependabot[bot] commented 7 months ago

Updates the requirements on google-cloud-env to permit the latest version.

Release notes

Sourced from google-cloud-env's releases.

google-cloud-env: v2.0.1

2.0.1 (2023-12-01)

Bug Fixes

Bad response status or flavor headers no longer signal positive metadata existence (#61)

Increase token expiry buffer to three and a half minutes (#59)

Changelog

Sourced from google-cloud-env's changelog.

2.0.1 (2023-12-01)

Bug Fixes

Bad response status or flavor headers no longer signal positive metadata existence (#61)

Increase token expiry buffer to three and a half minutes (#59)

2.0.0 (2023-11-14)

This is a major overhaul of the mechanisms underlying this gem, to improve reliability and provide better mocking interfaces. Environment interrogation calls are unchanged, but the mocking override parameters from 1.x have been removed in favor of the new interfaces, hence the semver-major version bump.

This version has not yet added explicit calls for detecting newer runtimes such as Cloud Run and Cloud Functions. Those will come in the near future.

Features

Update minimum Ruby version to 2.7

Provide access objects for information sources (such as environment variables, file system, and metadata server)

Each access object has an interface for providing mock data for testing

Much more robust retry policy and detection mechanisms for the metadata server

Provide ensure_metadata and lookup_metadata_response calls at the top level interface

1.7.0 (2023-05-15)

Features

Update minimum Ruby version to 2.6 (#34)

1.6.0 (2022-03-21)

Support for Faraday 2

1.5.0 (2021-03-08)

Features

Drop support for Ruby 2.4 and add support for Ruby 3.0

1.4.0 / 2020-10-12

Features

Honor GCE_METADATA_HOST environment variable

1.3.3 / 2020-07-10

Bug Fixes

Project ID logic honors GOOGLE_CLOUD_PROJECT

1.3.2 / 2020-05-28

... (truncated)

Commits

d0e94f5 chore(main): release google-cloud-env 2.0.1 (#60)
7fb9b6a fix: Bad response status or flavor headers no longer signal positive metadata...
d6105ee fix: Increase token expiry buffer to three and a half minutes (#59)
d417266 chore(main): release google-cloud-env 2.0.0 (#47)
52f767e chore: Fix release-please config (#58)
63877f2 docs: Update readme for 2.0 release (#57)
20778cd chore: Fix up some of the docs from recent PRs (#56)
cc9d197 chore(deps): update actions/github-script action to v7 (#55)
e221dc7 chore: Rework some of the compute-metadata logic (#54)
0df3a76 chore(deps): update actions/setup-node action to v4 (#44)
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 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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

0x73746F70626F74686572696E676D65 commented 4 months ago

Hi, can you please merge this? I'd like to help but i cant see the CI logs sadly.