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 all dependencies #19

Merged
merged 3 commits into from
Jan 7, 2025
Merged

chore(deps): update all dependencies #19

merged 3 commits into from
Jan 7, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
ansible (source) >=10.4,<10.5 -> >=10.7,<10.8 age adoption passing confidence minor
ansible-lint (changelog) >=24.9,<24.10 -> >=24.12,<24.13 age adoption passing confidence minor
ansible.posix 1.6.0 -> 1.6.2 age adoption passing confidence galaxy-collection patch
community.general 9.4.0 -> 9.5.3 age adoption passing confidence galaxy-collection minor
external-secrets 0.10.4 -> 0.12.1 age adoption passing confidence minor
external-secrets-source v0.10.4 -> v0.12.1 age adoption passing confidence minor
external-snapshotter-source v8.1.0 -> v8.2.0 age adoption passing confidence minor
mike-engel/jwt-cli 6.1.1 -> 6.2.0 age adoption passing confidence minor
reloader 1.1.0 -> 1.2.0 age adoption passing confidence minor
traefik (source) 32.0.0 -> 32.1.1 age adoption passing confidence minor
traefik-source v32.0.0 -> v32.1.1 age adoption passing confidence minor
victoria-metrics-k8s-stack 0.25.17 -> 0.33.2 age adoption passing confidence minor
victoriametrics/operator v0.48.1 -> v0.51.2 age adoption passing confidence minor

Release Notes

ansible-community/ansible-build-data (ansible)

v10.7.0

Compare Source

v10.6.0

Compare Source

v10.5.0

Compare Source

ansible/ansible-lint (ansible-lint)

v24.12.2

Compare Source

Enhancements

Bugfixes

Note this this changelog entry contains changes also included in the two yanked releases before it.

v24.12.1: (yanked)

Compare Source

Enhancements

Bugfixes

v24.12.0: (yanked)

Compare Source

Enhancements

Bugfixes

v24.10.0

Compare Source

Enhancements

Bugfixes

ansible-collections/ansible.posix (ansible.posix)

v1.6.2

Compare Source

======

Release Summary

This is the bugfix release of the stable version ansible.posix collection.
This changelog contains all changes to the modules and plugins
in this collection that have been added after the release of
ansible.posix 1.6.1.

Bugfixes

v1.6.1

Compare Source

======

Release Summary

This is the bugfix release of the stable version ansible.posix collection.
This changelog contains all changes to the modules and plugins
in this collection that have been added after the release of
ansible.posix 1.6.1.

Bugfixes

ansible-collections/community.general (community.general)

v9.5.3

Compare Source

See https://github.com/ansible-collections/community.general/blob/stable-9/CHANGELOG.md for all changes.

v9.5.2

Compare Source

See https://github.com/ansible-collections/community.general/blob/stable-9/CHANGELOG.md for all changes.

external-secrets/external-secrets (external-secrets)

v0.12.1

Compare Source

RELEASE VERSION

My apologies, when creating the release, 0.12.0 failed. The branch and tag however, have been created and I was unable to delete them. Thus, the version has been increased to 0.12.1 after the fix and now that's the current version. I hand updated the release notes to include everyone into the changes.

BREAKING CHANGES

The following breaking changes have been introduced into this release:

  • Permission update for AWS provider adding BulkFetch when getting multiple secrets ( significant API reduce but comes with adding a permission for bulk endpoint )
  • fixed a typo for a generator in the json tag where before it was ecrRAuthorizationTokenSpec with an extra R
  • We standardized the GCP Secrets Manager Metadata structure for PushSecrets ( be aware that existing manifests will stop working until updated to the standardized version ) for more info see https://github.com/external-secrets/external-secrets/pull/4210

Images

Image: ghcr.io/external-secrets/external-secrets:v0.12.1
Image: ghcr.io/external-secrets/external-secrets:v0.12.1-ubi
Image: ghcr.io/external-secrets/external-secrets:v0.12.1-ubi-boringssl

What's Changed

Full Changelog: external-secrets/external-secrets@v0.11.0...v0.12.1

v0.11.0

Compare Source

Deprecation of OLM Releases

As of 0.11.0 is the last release available for OLM until further notice. Depending on the way this goes, we might still have OLM support (ideally with a properly built operator for that), but for sure in a different support scheme as to not overload maintainers anymore.
Also a valid note - you can still use 0.11.0 OLM release and the newest ESO images, you just need to set image.tag appropriately in your setup.

Kubernetes API load and significant decrease

A new way of reconciling external secrets has been added with pull request #​4086.

This significantly reduces the number of API calls that we make to the kubernetes API server.

  1. Memory usage might increase if you are not already using --enable-secrets-caching
    1. If you are using --enable-secrets-caching and want to decrease memory usage at the expense of slightly higher API usage, you can disable it and only enable --enable-managed-secrets-caching (which is the new default)
  2. In ALL cases (even when CreationPolicy is Merge), if a data key in the target Secret was created by the ExternalSecret, and it no longer exists in the template (or data/dataFrom), it will be removed from the target secret:
    1. This might cause some peoples secrets to be "cleaned of data keys" when updating to 0.11.
    2. Previously, the behaviour was undefined, and confusing because it was sort of broken when the template feature was added.
    3. The one exception is that ALL the data suddenly becomes empty and the DeletionPolicy is retain, in which case we will not even report and error, just change the SecretSynced message to explain that the secret was retained.
  3. When CreationPolicy is Owner, we now will NEVER retain any keys and fully calculate the "desired state" of the target secret each loop:
    1. This means that some peoples secrets might have keys removed when updating to 0.11.
Generators and ClusterGenerator

We added ClusterGenerators and Generator caching as well. This might create some problems in the way generators are defined now.

CRD Admission Restrictions

All of the CRDs now have proper kubebuilder markers for validation. This might surprise someone leaving out some data that was essentially actually required or expected in a certain format. This is now validated in #​4104.

Images

Image: ghcr.io/external-secrets/external-secrets:v0.11.0
Image: ghcr.io/external-secrets/external-secrets:v0.11.0-ubi
Image: ghcr.io/external-secrets/external-secrets:v0.11.0-ubi-boringssl

What's Changed
New Contributors

Full Changelog: external-secrets/external-secrets@v0.10.7...v0.11.0

v0.10.7

Compare Source

Image: ghcr.io/external-secrets/external-secrets:v0.10.7
Image: ghcr.io/external-secrets/external-secrets:v0.10.7-ubi
Image: ghcr.io/external-secrets/external-secrets:v0.10.7-ubi-boringssl

What's Changed
New Contributors

Full Changelog: external-secrets/external-secrets@v0.10.6...v0.10.7

v0.10.6

Compare Source

Image: ghcr.io/external-secrets/external-secrets:v0.10.6
Image: ghcr.io/external-secrets/external-secrets:v0.10.6-ubi
Image: ghcr.io/external-secrets/external-secrets:v0.10.6-ubi-boringssl

What's Changed

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" in timezone Europe/Paris, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 force-pushed the renovate/all branch 4 times, most recently from 363400c to ae6fb6e Compare November 27, 2024 17:03
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 7590db4 to d30a0a8 Compare December 5, 2024 07:39
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from c2942e7 to 0a07af8 Compare December 17, 2024 15:15
@renovate renovate bot force-pushed the renovate/all branch 8 times, most recently from acd3671 to b8279d9 Compare December 24, 2024 19:25
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 4d73dd7 to 728f5ca Compare January 6, 2025 08:39
Copy link
Contributor Author

renovate bot commented Jan 7, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@orblazer orblazer merged commit 58e4bf3 into main Jan 7, 2025
1 check passed
@orblazer orblazer deleted the renovate/all branch January 7, 2025 18:52
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.

2 participants