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(gcp scalers): Restore previous time horizon to fix missing metrics and properly close the connecctions #5452
• fix(prometheus-scaler): AWS signv4 parses region if provided #5421
• UPGRADE FAILED: cannot patch "security-services" with kind ScaledObject: Timeout: request did not complete within requested timeout - context deadline exceeded #5487
• Fixed the issue#5484 with inaccurate version label in release asset #5518
• fix: Place the changelog entry in unreleased section #5519

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