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

chore(deps): update module github.com/rancher/lasso to v0.2.0 (release/v0.1) #140

Conversation

renovate-rancher[bot]
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
github.com/rancher/lasso require minor v0.0.0-20240415182150-5993b260dd08 -> v0.2.0

Release Notes

rancher/lasso (github.com/rancher/lasso)

v0.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/rancher/lasso/commits/v0.2.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Copy link
Contributor Author

renovate-rancher bot commented Feb 1, 2025

ℹ Artifact update notice

File name: controller-runtime/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 22 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.21 -> 1.23.6
k8s.io/apimachinery v0.29.3 -> v0.31.1
k8s.io/client-go v0.29.3 -> v0.31.1
github.com/cespare/xxhash/v2 v2.2.0 -> v2.3.0
github.com/davecgh/go-spew v1.1.1 -> v1.1.2-0.20180830191138-d8f796af33cc
github.com/go-logr/logr v1.3.0 -> v1.4.2
github.com/go-openapi/swag v0.22.3 -> v0.22.4
github.com/google/uuid v1.3.0 -> v1.6.0
github.com/prometheus/client_golang v1.16.0 -> v1.19.1
github.com/prometheus/client_model v0.4.0 -> v0.6.1
github.com/prometheus/common v0.44.0 -> v0.55.0
github.com/prometheus/procfs v0.12.0 -> v0.15.1
golang.org/x/net v0.20.0 -> v0.26.0
golang.org/x/oauth2 v0.16.0 -> v0.21.0
golang.org/x/sys v0.16.0 -> v0.21.0
golang.org/x/term v0.16.0 -> v0.21.0
golang.org/x/text v0.14.0 -> v0.16.0
google.golang.org/protobuf v1.33.0 -> v1.34.2
k8s.io/api v0.29.3 -> v0.31.1
k8s.io/klog/v2 v2.110.1 -> v2.130.1
k8s.io/kube-openapi v0.0.0-20231010175941-2dd684a91f00 -> v0.0.0-20240228011516-70dd3763d340
k8s.io/utils v0.0.0-20230726121419-3b25d923346b -> v0.0.0-20240711033017-18e509b52bc8
sigs.k8s.io/yaml v1.3.0 -> v1.4.0

@renovate-rancher renovate-rancher bot requested a review from a team as a code owner February 1, 2025 04:36
@renovate-rancher renovate-rancher bot force-pushed the renovate/release/v0.1-github.com-rancher-lasso-0.x branch from aa06316 to c9d3404 Compare February 5, 2025 04:37
@renovate-rancher renovate-rancher bot force-pushed the renovate/release/v0.1-github.com-rancher-lasso-0.x branch from c9d3404 to 90a0db3 Compare February 6, 2025 23:37
@rohitsakala
Copy link
Member

Closing this since this is wierd, the lasso new version is trying to update in downgraded version release branch.

@rohitsakala rohitsakala closed this Feb 7, 2025
@rohitsakala rohitsakala deleted the renovate/release/v0.1-github.com-rancher-lasso-0.x branch February 7, 2025 20:01
Copy link
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v0.2.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant