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: CVE-2024-45337 #6422
• fix: ensure consistent JSON log format for automaxprocs #6335
• Upgrade to the latest new-relic-go v2 client #6325
• refactor: replace experimental maps and slices with stdlib #6372
• fix: Selenium Grid scaler exposes sum of pending and ongoing sessions to KDEA #6368
• fix: scaledjobs stuck as not ready #6329
• fix: Paused ScaledObject count is reported correctly after operator restart #6322
• Bump go and deps #6434

Timeline

We aim to release this release in the week of <week range, example March 27-31>.

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