Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 25, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sigs.k8s.io/yaml v1.4.0 -> v1.5.0 age adoption passing confidence

Release Notes

kubernetes-sigs/yaml (sigs.k8s.io/yaml)

v1.5.0

Compare Source

Full Changelog: kubernetes-sigs/yaml@v1.4.0...v1.5.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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jun 25, 2025
@sourcery-ai
Copy link

sourcery-ai bot commented Jun 25, 2025

Reviewer's Guide

This PR bumps the sigs.k8s.io/yaml dependency to v1.5.0 (including its redirected go.yaml.in/yaml/v2 replacement) and refreshes the vendored YAML package by removing deprecated goyaml.v2 artifacts and adding the new module layout.

File-Level Changes

Change Details Files
Upgrade YAML dependency version and include its redirected module
  • Change sigs.k8s.io/yaml requirement from v1.4.0 to v1.5.0
  • Add go.yaml.in/yaml/v2 v2.4.2 as an indirect dependency
  • Update go.sum to reflect the new module versions
go.mod
go.sum
Restructure vendor directory for YAML module migration
  • Add vendor/go.yaml.in/yaml/v2 directory with README.md, yaml.go, and .travis.yml
  • Remove deprecated files under vendor/sigs.k8s.io/yaml (OWNERS, .travis.yml, yaml_go110.go)
  • Refresh vendor/modules.txt and existing yaml.go to align with v1.5.0
vendor/go.yaml.in/yaml/v2/.travis.yml
vendor/go.yaml.in/yaml/v2/README.md
vendor/go.yaml.in/yaml/v2/yaml.go
vendor/sigs.k8s.io/yaml/.travis.yml
vendor/sigs.k8s.io/yaml/goyaml.v2/OWNERS
vendor/sigs.k8s.io/yaml/yaml_go110.go
vendor/modules.txt
vendor/sigs.k8s.io/yaml/yaml.go

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Jun 26, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 26, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, renovate[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/sigs.k8s.io-yaml-1.x branch from 1734bc5 to c8264a0 Compare June 26, 2025 10:35
@openshift-ci openshift-ci bot removed the lgtm label Jun 26, 2025
@Luap99
Copy link
Member

Luap99 commented Jun 26, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Jun 26, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 8003ce3 into main Jun 26, 2025
13 of 14 checks passed
@renovate renovate bot deleted the renovate/sigs.k8s.io-yaml-1.x branch June 26, 2025 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved dependencies Pull requests that update a dependency file lgtm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants