feat: update appVersion to v2.51.3

[kleberbaum]

Definition of Ready

• I am happy with the code
• Short description of the feature/issue is added in the pr description
• PR is linked to the corresponding user story
• Acceptance criteria are met
• All open todos and follow ups are defined in a new ticket and justified
• Deviations from the acceptance criteria and design are agreed with the PO and documented.
• No debug or dead code
• My code has no repetitions
• Documentation/examples are up-to-date
• All non-functional requirements are met
• If possible, the test configuration is adjusted so acceptance tests cover my changes

What is the current behavior?
The previously implemented workflow functionality from PR zitadel/zitadel#4544, which automatically triggered a webhook post-ZITADEL release, has been removed. Consequently, the bump workflow (introduced in #43 and discussed in Issue #105) is no longer dispatched, as it depends on this mechanism. This issue is also tracked in the Product Management Backlog under item 30889015.

What is the new behavior?
This PR updates the ZITADEL version to v2.51.0 manually.

What could be a permanent solution?
To resolve Issue #105 it may be necessary to reimplement the changes from PR zitadel/zitadel#4544 in Current ZITADEL Release Workflow.

      - uses: tibdex/github-app-token@v1
        id: generate-token
        with:
          app_id: ${{ secrets.APP_ID }}
          private_key: ${{ secrets.APP_PRIVATE_KEY }}
      - name: Bump Chart Version
        uses: peter-evans/repository-dispatch@v2
        if: steps.semantic.outputs.new_release_published == 'true' && github.ref == 'refs/heads/main'
        with:
          token: ${{ steps.generate-token.outputs.token }}
          repository: zitadel/zitadel-charts
          event-type: zitadel-released
          client-payload: '{"semanticoutputs": "${{ steps.semantic.outputs }}"}'

However, the current bump workflow does not appear to be functional, as indicated by .

Your feedback and suggestions would be greatly appreciated.

[kleberbaum]

It appears that the check failure was not caused by a bug, but rather a minor hiccup in the GitHub workflow, especially since it was successfully with v2.51.0. I suggest rerunning the check for K8s version v1.21 to see if the problem persists.

[eliobischof]

@kleberbaum the flakiness is fixed on main.
Please merge back main. It seems I don't have the permission to push to your repo myself.

[eliobischof]

depends on #202

[kleberbaum]

It seems like someone jumped the queue #199 😄

[kleberbaum]

Could we expedite the merge?😅 I'm relying on the updated Helm chart for a project deployment that utilizes the new email features introduced in Zitadel. @eliobischof

[rhizoet]

The version v2.51.3 has been released. Maybe you can update to this version before the merge?

[eliobischof]

@kleberbaum @rhizoet are you aware that you can always overwrite the charts default appVersion in your local helm release config?

[kleberbaum]

Thanks for the merge 🎉 I see the ZITADEL version tag in values.yaml can be overwritten. @eliobischof @rhizoet

However, I prefer upgrading deployments like this:

# Add ZITADEL repository
helm repo add zitadel https://charts.zitadel.com

# Get deployment values
helm get values zitadel -n mynamespace > zitadel-values.yaml

# Upgrade to the latest or a specific version
helm upgrade zitadel zitadel/zitadel -f zitadel-values.yaml -n mynamespace
helm upgrade zitadel zitadel/zitadel --version 7.14.0 -f zitadel-values.yaml -n mynamespace

This method ensures clear version tracking in helm history.

helm history zitadel -n mynamespace

[eliobischof]

Thanks for the merge 🎉 I see the ZITADEL version tag in values.yaml can be overwritten. @eliobischof @rhizoet

However, I prefer upgrading deployments like this:

# Add ZITADEL repository
helm repo add zitadel https://charts.zitadel.com

# Get deployment values
helm get values zitadel -n mynamespace > zitadel-values.yaml

# Upgrade to the latest or a specific version
helm upgrade zitadel zitadel/zitadel -f zitadel-values.yaml -n mynamespace
helm upgrade zitadel zitadel/zitadel --version 7.14.0 -f zitadel-values.yaml -n mynamespace

This method ensures clear version tracking in helm history.

helm history zitadel -n mynamespace

Ah, I didn't consider that 😃 thanks for sharing