☂️ Release Woodpecker v3.10

[xoxys]

Prerequisites

• Prepare docs PR for new version and delete old versions (keep only the last three minor versions for the current major version)
  • Run make generate locally to update the automatically generated CLI documentation
  • Copy docs/docs to docs/versioned_docs/version-<version> and delete old versions
  • Create docs/versioned_sidebars/version-<version>-sidebars.json and delete old ones
  • Add new version to docs/versions.json and delete old versions
  • Add new version to the version list in docs/src/pages/versions.md
• Announce the release in the maintainer chat and ask for pending blockers

Release

• Test the latest container images to make sure they work as expected
• Update https://ci.woodpecker.org to the latest version of next and verify that it works as expected
• Merge documentation PR (shortly before release)
• Merge the release PR to start the release pipeline

Post-release

• Release the Helm Chart. If renovate has not created the upgrade PR already, manually trigger it from the Dependency Dashboard.
• Announce release in relevant chats and on social media platforms
  • Mastodon (check if already posted from the release pipeline)
  • Bluesky (check if already posted from the release pipeline)
  • Matrix

[xoxys]

Current blockers:

• Acquire write lock for pipeline creation into the database #5534 @6543 will this be resolved soon? Otherwise, I'm fine to release 3.10 without it
• duplicate column name: oauth_client_id #5538. I'm a bit worried about this issue. This might be a hiccup during upgrade between next versions as we had to fix the migration multiple times, but I still don't understand how the DB gets into the state reported by the user.

[6543]

I dont want to give an ETA so release without if nothing else is blocking ...

[6543]

@xoxys thanks for beeing an release manager :)

do you intent to make the social posts or wait for 3.11?

[xoxys]

I dont have access and the CI did not posted them due to the broken release. So someone else would have to do that or share the credentials in vaultwarden with me.

[qwerty287]

Did the posts. Is this issue finished?

[6543]

thanks :)