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

fix(deps): update module github.com/cyphar/filepath-securejoin to v0.3.6 #2275

Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 17, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/cyphar/filepath-securejoin v0.3.5 -> v0.3.6 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

cyphar/filepath-securejoin (github.com/cyphar/filepath-securejoin)

v0.3.6

Compare Source

This release lowers the minimum Go version to Go 1.18 as well as some
library dependencies, in order to make it easier for folks that need to
backport patches using the new filepath-securejoin API onto branches
that are stuck using old Go compilers. For users using Go >= 1.21, this
release contains no functional changes.

  • The minimum Go version requirement for filepath-securejoin is now Go 1.18
    (we use generics internally).

    For reference, [email protected] somewhat-arbitrarily bumped the
    Go version requirement to 1.21.

    While we did make some use of Go 1.21 stdlib features (and in principle Go
    versions <= 1.21 are no longer even supported by upstream anymore), some
    downstreams have complained that the version bump has meant that they have to
    do workarounds when backporting fixes that use the new filepath-securejoin
    API onto old branches. This is not an ideal situation, but since using this
    library is probably better for most downstreams than a hand-rolled
    workaround, we now have compatibility shims that allow us to build on older
    Go versions.

  • Lower minimum version requirement for golang.org/x/sys to v0.18.0 (we
    need the wrappers for fsconfig(2)), which should also make backporting
    patches to older branches easier.

Signed-off-by: Aleksa Sarai [email protected]


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.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 17, 2024
Copy link

Ephemeral COPR build failed. @containers/packit-build please check.

@rhatdan
Copy link
Member

rhatdan commented Dec 17, 2024

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm label Dec 17, 2024
Copy link
Contributor

openshift-ci bot commented Dec 17, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

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

@openshift-merge-bot openshift-merge-bot bot merged commit 4ddb120 into main Dec 17, 2024
14 of 15 checks passed
@renovate renovate bot deleted the renovate/github.com-cyphar-filepath-securejoin-0.x branch December 17, 2024 13:05
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.

3 participants