Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release: v2.13.1 #5504

Closed
21 tasks done
JorTurFer opened this issue Feb 13, 2024 · 9 comments
Closed
21 tasks done

Release: v2.13.1 #5504

JorTurFer opened this issue Feb 13, 2024 · 9 comments
Assignees
Labels
governance release-management All issues related to how we release

Comments

@JorTurFer
Copy link
Member

JorTurFer commented Feb 13, 2024

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

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
@tomkerkhove
Copy link
Member

I'm happy to handle the release itself if we are looking for a release captain.

@JorTurFer We did not fill in an ETA, is that on purpose?

@JorTurFer
Copy link
Member Author

We did not fill in an ETA, is that on purpose?

Mistake, but I have no idea about the ETA either xD Next week?

@zroubalik
Copy link
Member

We did not fill in an ETA, is that on purpose?

Mistake, but I have no idea about the ETA either xD Next week?

I'd wait with the release a bit.

@JorTurFer
Copy link
Member Author

Last release was "last month" but I can't check when 😢
I'd aim to a month and a half after the last releate

@zroubalik
Copy link
Member

For me, the main purpose of this issue is to track issues that we might want to include, to not lost track of them.

@seddarj
Copy link

seddarj commented Feb 23, 2024

Hello, seeing issues related to what was fixed in #5452. Any ETA on when you will release 2.13.1?

@JorTurFer
Copy link
Member Author

JorTurFer commented Feb 29, 2024

Hello, seeing issues related to what was fixed in #5452. Any ETA on when you will release 2.13.1?

@seddarj , the the new version has been published, KEDA v2.13.1 and for helm v2.13.2

@JorTurFer
Copy link
Member Author

Only the announces are left, so I'll publish them tomorrow during the morning

@JorTurFer
Copy link
Member Author

Release completed!

@github-project-automation github-project-automation bot moved this from To Triage to Ready To Ship in Roadmap - KEDA Core Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
governance release-management All issues related to how we release
Projects
Archived in project
Development

No branches or pull requests

4 participants