Release: v2.16

[JorTurFer]

This issue template is used to track the rollout of a new KEDA version.

For the full release process, we recommend reading this document.

Required items

• List items that are still open, but required for this release

Timeline

We aim to release this release in the week of October 30th November 3rd

Progress

• Prepare changelog
• Welcome message supported versions are up-to-date
• Add the new version to GitHub Bug report template
• Best effort version bump for dependencies, example: #5400
  • Update k8s go modules and pin to the 2nd most recent minor version
  • Check if new Go has been released and if KEDA can be safely built by it
  • Update linters and build pipelines if Go has been bumped, example: #5399
• Best effort changelog cleanup, sometimes the notes can be a little inconsistent, example: #5398
• Create KEDA release
• Publish new documentation version
• Setup continuous container scanning with Snyk
• Prepare & ship Helm chart
• Create a new issue in KEDA OLM repository
• Prepare next release
• Provide update in Slack
• Tweet about new release

[JorTurFer]

Nobody has included anything to be merged before the release and I think that e2e test can be merged later on (although they aren't 100% stables, they are quite better), so the release will continue with the plan as expected.
FYI @zroubalik @wozniakjan @SpiritZhou

[wozniakjan]

nothing from me directly but if we could fix #6255, that would be great. Because if I understand correctly, July 22, 2025, the GCP pub/sub scaler will need to support the promql syntax.

[JorTurFer]

So, should we postpone the release until next week? Is anybody working on #6255?

[JorTurFer]

There are currently 41 PR and maybe there are some of them interesting, but I haven't had time to review them, during the long weekend I can review them and maybe any other can do the same, including more features if we postpone the release for a week 🤔

[SpiritZhou]

There are currently 41 PR and maybe there are some of them interesting, but I haven't had time to review them, during the long weekend I can review them and maybe any other can do the same, including more features if we postpone the release for a week 🤔

I reviewed some of them and some simple scaler refactor PRs are OK to be merged.

[wozniakjan]

So, should we postpone the release until next week? Is anybody working on #6255?

I don't think there is anyone working on #6255 actively, but I'm wondering if we can just add a query metadata field to the GCP pub/sub scaler and reuse code from the prometheus
https://keda.sh/docs/1.4/scalers/prometheus/#trigger-specification

maybe that is what you mentioned in #6255 (comment)?

[JorTurFer]

we are facing with issues related with docker rate limit making the e2e tests flaky:

We are going to include a proxy via ACR or ECR or so, but in the meantime we decided to postpone the release to the next week