ESO Chart upgrade to version 0.17.0

[vbontempi]

Description

IMPORTANT NOTE: this PR must be merged ONLY AFTER #124 is merged and a version is generated

This PR contains the following updates:

Package	Update	Change
external-secrets	minor	0.16.2 -> 0.17.0

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release Notes

To avoid external secrets operator deployment disruption on the secrets synchronisation, it is strongly suggested to upgrade to version 1.5.0 before upgrading to this new major version

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

v0.17.0

Compare Source

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

BREAKING CHANGE

v0.17.0 Stops serving v1beta1 apis. You need to update your manifests from v1beta1 to v1 prior to updating from v0.16 to v0.17.

The only change needed is upgrading your manifests to v1 (i.e. removing the beta1 from v1beta1).

Be sure to do that to all your manifests prior to bumping to v0.17.0! v0.16.2 already supports v1 so this process should be smooth.

What's Changed

• chore: update helm charts v0.16.2 by @​Skarlso in https://github.com/external-secrets/external-secrets/pull/4748
• fix: typo on delete method for repo by @​gusfcarvalho in https://github.com/external-secrets/external-secrets/pull/4750
• fix: Show Errors from Github by @​Alexander-Cairns in https://github.com/external-secrets/external-secrets/pull/4753
• doc(openbao): add information about it working with vault provider by @​eyenx in https://github.com/external-secrets/external-secrets/pull/4755
• Gc/fix/gcp pushsecret location replication by @​gusfcarvalho in https://github.com/external-secrets/external-secrets/pull/4751
• chore: unserve v1beta1 and mark it as deprecated by @​gusfcarvalho in https://github.com/external-secrets/external-secrets/pull/4758
• fix: not releasing helm charts when its already released by @​gusfcarvalho in https://github.com/external-secrets/external-secrets/pull/4771
• fix: remove comment from helm by @​gusfcarvalho in https://github.com/external-secrets/external-secrets/pull/4772
• infisical: support secrets within paths for data references by @​lgo in https://github.com/external-secrets/external-secrets/pull/4305
• chore(deps): bump pyyaml-env-tag from 0.1 to 1.0 in /hack/api-docs by @​dependabot in https://github.com/external-secrets/external-secrets/pull/4761
• chore(deps): bump platformdirs from 4.3.7 to 4.3.8 in /hack/api-docs by @​dependabot in https://github.com/external-secrets/external-secrets/pull/4762
• chore(deps): bump mkdocs-material from 9.6.12 to 9.6.13 in /hack/api-docs by @​dependabot in https://github.com/external-secrets/external-secrets/pull/4763
• chore(deps): bump golang from 1.24.2 to 1.24.3 by @​dependabot in https://github.com/external-secrets/external-secrets/pull/4764
• chore(deps): bump golang from 1.24.2-bookworm to 1.24.3-bookworm in /e2e by @​dependabot in https://github.com/external-secrets/external-secrets/pull/4765
• chore(deps): bump actions/setup-go from 5.4.0 to 5.5.0 by @​dependabot in https://github.com/external-secrets/external-secrets/pull/4766
• Cache separate vault clients for each namespace if necessary by @​ChristianCiach in https://github.com/external-secrets/external-secrets/pull/4706
• chore(deps): bump dependabot/fetch-metadata from 2.3.0 to 2.4.0 by @​dependabot in https://github.com/external-secrets/external-secrets/pull/4768
• feat: improve code integration api by @​gusfcarvalho in https://github.com/external-secrets/external-secrets/pull/4777
• chore: update dependencies by @​eso-service-account-app in https://github.com/external-secrets/external-secrets/pull/4770
• chore(deps): bump actions/dependency-review-action from 67d4f4b to 8805179 by @​dependabot in https://github.com/external-secrets/external-secrets/pull/4767
• fix: adds releases to stability and support by @​gusfcarvalho in https://github.com/external-secrets/external-secrets/pull/4776
• Update docs/example for ECR token generator by @​Moulick in https://github.com/external-secrets/external-secrets/pull/4773
• feat: add 1Password SDK based provider by @​Skarlso in https://github.com/external-secrets/external-secrets/pull/4628
• chore: updates stability support for 0.17.0 by @​gusfcarvalho in https://github.com/external-secrets/external-secrets/pull/4779
• fix: update provider examples to use apiVersion external-secrets.io/v1 by @​rowanruseler in https://github.com/external-secrets/external-secrets/pull/4757

New Contributors

• @​Alexander-Cairns made their first contribution in https://github.com/external-secrets/external-secrets/pull/4753
• @​eyenx made their first contribution in https://github.com/external-secrets/external-secrets/pull/4755
• @​ChristianCiach made their first contribution in https://github.com/external-secrets/external-secrets/pull/4706
• @​Moulick made their first contribution in https://github.com/external-secrets/external-secrets/pull/4773
• @​rowanruseler made their first contribution in https://github.com/external-secrets/external-secrets/pull/4757

Full Changelog: external-secrets/external-secrets@v0.16.2...v0.17.0

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[ocofaigh]

@vbontempi I have just merged #124 and generated v1.5.0 of the module.
I think we should make this PR a new major version release because consumers are going to have to upgrade to it from v1.5.0 - thoughts?

[vbontempi]

@vbontempi I have just merged #124 and generated v1.5.0 of the module. I think we should make this PR a new major version release because consumers are going to have to upgrade to it from v1.5.0 - thoughts?

PR #124 was marked as patch release but I think you did the right thing to generate a minor version.
About the new major version, I am not sure it is a new major version as with the two steps upgrade there is no breaking change on user side, unless they previously don't step into v1.5.0
But maybe using a new major version helps with underlying the impact of the change, so I am ok with using major version

[ocofaigh]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 2.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀