Build(deps): Bump google.golang.org/api from 0.257.0 to 0.276.0#1098
Build(deps): Bump google.golang.org/api from 0.257.0 to 0.276.0#1098dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [google.golang.org/api](https://github.com/googleapis/google-api-go-client) from 0.257.0 to 0.276.0. - [Release notes](https://github.com/googleapis/google-api-go-client/releases) - [Changelog](https://github.com/googleapis/google-api-go-client/blob/main/CHANGES.md) - [Commits](googleapis/google-api-go-client@v0.257.0...v0.276.0) --- updated-dependencies: - dependency-name: google.golang.org/api dependency-version: 0.276.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Summary by CodeRabbit
WalkthroughUpdated Go toolchain version from 1.24.13 to 1.25.0 in Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dependabot[bot] The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
needs-ok-to-test
|
Hi @dependabot[bot]. Thanks for your PR. I'm waiting for a openshift-online member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@go.mod`:
- Line 3: CI workflows still pin older Go versions; update all references of the
go-version/matrix entries in the GitHub workflow files that configure
actions/setup-go (e.g., the go-version key and any matrix entries in the
publish-release and check-pull-request workflows) from 1.22/1.23 to 1.25.0 so
they match go.mod; ensure both the single go-version values and any matrix items
are changed to "1.25.0" and run a quick CI lint to validate the YAML.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 2528ac2d-560a-4c70-abad-b1be6800bd72
⛔ Files ignored due to path filters (1)
go.sumis excluded by!**/*.sum
📒 Files selected for processing (1)
go.mod
| module github.com/openshift-online/ocm-cli | ||
|
|
||
| go 1.24.13 | ||
| go 1.25.0 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Read-only verification: find Go version pins across CI/build/release config.
set -euo pipefail
echo "== go.mod/go.work directives =="
fd -HI '^(go\.mod|go\.work)$' -t f | xargs -r -I{} sh -c 'echo "--- {}"; sed -n "1,40p" "{}" | rg -n "^(go|toolchain)\s+" || true'
echo
echo "== CI/workflow/build files mentioning Go versions =="
rg -n --hidden --glob '!**/.git/**' --glob '!**/vendor/**' \
'(setup-go|go-version|GOVERSION|GO_VERSION|golang:|go1\.[0-9]+(\.[0-9]+)?)' \
.github/ Makefile Dockerfile\* \*.mk \*.yaml \*.yml 2>/dev/null || true
echo
echo "Expected: all version pins are >= 1.25 (or this bump should be split/adjusted)."Repository: openshift-online/ocm-cli
Length of output: 692
Update CI workflows to match the Go 1.25.0 requirement in go.mod.
The go.mod change to go 1.25.0 introduces a version mismatch with CI pipelines:
.github/workflows/publish-release.yamlis pinned to Go 1.23.github/workflows/check-pull-request.yamlis pinned to Go 1.22 and 1.23
This will cause CI failures. Update all workflow go-version pins to 1.25.0 to match the module requirement.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@go.mod` at line 3, CI workflows still pin older Go versions; update all
references of the go-version/matrix entries in the GitHub workflow files that
configure actions/setup-go (e.g., the go-version key and any matrix entries in
the publish-release and check-pull-request workflows) from 1.22/1.23 to 1.25.0
so they match go.mod; ensure both the single go-version values and any matrix
items are changed to "1.25.0" and run a quick CI lint to validate the YAML.
openshift-ci
Bot
added
the
needs-rebase
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Bumps google.golang.org/api from 0.257.0 to 0.276.0.
Release notes
Sourced from google.golang.org/api's releases.
... (truncated)
Changelog
Sourced from google.golang.org/api's changelog.
... (truncated)
Commits
006c411chore(main): release 0.276.0 (#3562)54188cffeat(all): auto-regenerate discovery clients (#3566)7c11b5afeat(all): auto-regenerate discovery clients (#3565)2450322chore: embargo discoveryengine:v1 from generation (#3564)0c9c60fchore: embargo discoveryengine:v1alpha from generation (#3563)dd3f1bbfeat(all): auto-regenerate discovery clients (#3561)d43aa15chore(main): release 0.275.0 (#3558)9437d4dfeat(all): auto-regenerate discovery clients (#3560)0a62c64chore(all): update cloud.google.com/go/auth to v0.20.0 (#3559)2b2ef99feat(all): auto-regenerate discovery clients (#3557)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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)