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

• fix: Correct parse error ActiveMQ #7245
• fix: metricUnavailableValue parameter not working in Datadog scaler #7241
• Fix race condition in paused-replicas annotation #7233
• fix: use TriggerError when all ScaledJob triggers fail #7205
• Fix transfer-hpa-ownership panic when hpa name not provided #7260
• bump actions and go version #7295

Nice to have

• fix: restore HPA behavior when paused-scale-in/out annotation is deleted #7291
• refactor: remove unused scaledObjectMetricSpecs variable #7292
• fix: handle requestScaleLoop error in ScaledObject controller #7273

Timeline

We aim to release this release in the week of December 8

Progress

• Prepare changelog
  • Rename Unreleased to the new version and make sure new empty Unreleased section with subsections exists
  • Best effort changelog cleanup, sometimes the notes can be a little inconsistent, example: #5398
• Update Kubernetes compatibility (usually 3 versions, bump +1 from previous KEDA version)
  • Welcome message supported versions are up-to-date
  • Update KEDA docs, example: #1633
  • Update Charts runners, example #782
• Add new KEDA version to [GitHub Bug report](https://github.com/kedacore/keda/blob/main/.github/
• 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
  • Update envtest version in the Makefile to match k8s version in go.mod
• 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
• Provide update in Slack
• Tweet about new release
• Create a new release tracking issue for the next version and set there preliminary date based on the schedule