fluxcd / image-automation-controller

GitOps Toolkit controller that patches container image tags in Git
https://fluxcd.io
Apache License 2.0
178 stars 72 forks source link

Bump the go-deps group across 1 directory with 3 updates #775

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 3 weeks ago

Bumps the go-deps group with 3 updates in the / directory: github.com/ProtonMail/go-crypto, github.com/cyphar/filepath-securejoin and github.com/go-git/go-billy/v5.

Updates github.com/ProtonMail/go-crypto from 1.1.0-alpha.5-proton to 1.1.0-beta.0-proton

Release notes

Sourced from github.com/ProtonMail/go-crypto's releases.

v1.1.0-beta.0-proton

This pre-release is v1.1.0-beta.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-beta.0

What's Changed

Full Changelog: https://github.com/ProtonMail/go-crypto/compare/v1.1.0-alpha.5...v1.1.0-beta.0

Commits
  • b04e354 Fix HMAC generation (#204)
  • 85bc845 Replace ioutil.ReadAll with io.ReadAll
  • 5f49c73 fix(v2): Adapt NewForwardingEntity to refactored NewEntity
  • 9aa010a fix(v2): Do not allow encrpytion with a forwarding key
  • 91c2e9e feat: Add symmetric keys to v2
  • 3f6d02a fix: Address warnings
  • da0a0cf feat: Add forwarding to v2 api
  • 0e6a359 fix: Address rebase on version 2 issues
  • c602a74 Use fingerprints instead of KeyIDs
  • 348b81d Create a copy of the encrypted key when forwarding
  • Additional commits viewable in compare view


Updates github.com/cyphar/filepath-securejoin from 0.3.2 to 0.3.4

Release notes

Sourced from github.com/cyphar/filepath-securejoin's releases.

v0.3.4

This release primarily includes a fix that blocked using filepath-securejoin in Kubernetes.

  • Previously, some testing mocks we had resulted in us doing import "testing" in non-_test.go code, which made some downstreams like Kubernetes unhappy. This has been fixed. (#32)

Thanks to all of the contributors who made this release possible:

Signed-off-by: Aleksa Sarai cyphar@cyphar.com

v0.3.3

This release primarily includes fixes for spurious errors we hit when checking that directories created by MkdirAll "look right". Upon further consideration, these checks were fundamentally buggy and didn't offer any practical protection anyway.

  • The mode and owner verification logic in MkdirAll has been removed. This was originally intended to protect against some theoretical attacks but upon further consideration these protections don't actually buy us anything and they were causing spurious errors with more complicated filesystem setups.
  • The "is the created directory empty" logic in MkdirAll has also been removed. This was not causing us issues yet, but some pseudofilesystems (such as cgroup) create non-empty directories and so this logic would've been wrong for such cases.

Thanks to all of the contributors who made this release possible:

Signed-off-by: Aleksa Sarai cyphar@cyphar.com

Changelog

Sourced from github.com/cyphar/filepath-securejoin's changelog.

[0.3.4] - 2024-10-09

Fixed

  • Previously, some testing mocks we had resulted in us doing import "testing" in non-_test.go code, which made some downstreams like Kubernetes unhappy. This has been fixed. (#32)

[0.3.3] - 2024-09-30

Fixed

  • The mode and owner verification logic in MkdirAll has been removed. This was originally intended to protect against some theoretical attacks but upon further consideration these protections don't actually buy us anything and they were causing spurious errors with more complicated filesystem setups.
  • The "is the created directory empty" logic in MkdirAll has also been removed. This was not causing us issues yet, but some pseudofilesystems (such as cgroup) create non-empty directories and so this logic would've been wrong for such cases.
Commits
  • fd16ade VERSION: release v0.3.4
  • 00e0710 godoc: update package documentation
  • 0cd6be1 README: fix reference to open_tree kernel requirements
  • 205046f README: add pkg.go.dev badge
  • ecb1b8e tests: procfs: clean up mock test hook
  • 3ec6eed CHANGELOG: mention #32 fix
  • 86e6182 merge #32 into cyphar/filepath-securejoin:main
  • 6864912 Isolate the testing import in test code
  • 4348fee openat: remove unused function
  • d0c7d67 merge #31 into cyphar/filepath-securejoin:main
  • Additional commits viewable in compare view


Updates github.com/go-git/go-billy/v5 from 5.5.0 to 5.6.0

Release notes

Sourced from github.com/go-git/go-billy/v5's releases.

v5.6.0

What's Changed

New Contributors

Full Changelog: https://github.com/go-git/go-billy/compare/v5.5.0...v5.6.0

Commits
  • 371e232 Merge pull request #85 from go-git/dependabot/github_actions/github/codeql-ac...
  • 5087c4c build: bump github/codeql-action from 3.26.10 to 3.26.11
  • 5f263c9 Merge pull request #84 from go-git/dependabot/github_actions/github/codeql-ac...
  • 18ec098 build: bump github/codeql-action from 3.26.8 to 3.26.10
  • c1ee0b9 Merge pull request #81 from evankanderson/iofs
  • b50bc97 Rename Wrap to New
  • 9745bbb Merge pull request #83 from go-git/dependabot/github_actions/github/codeql-ac...
  • d864d47 build: bump github/codeql-action from 3.26.7 to 3.26.8
  • b8c5b1b Prevent test failures on Windows, address feedback from pjbgf
  • 28f6c49 Fix test handling on go < 1.23
  • 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 major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 2 weeks ago

Looks like these dependencies are updatable in another way, so this is no longer needed.