chore: prepare release workflow for codegen 3.0#12720
Merged
ewaostrowska merged 1 commit into3.0.0from May 8, 2026
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a manual GitHub Actions “prepare release” workflow for the Swagger Codegen 3.0 line, plus supporting release helper scripts to validate version inputs, update release-related files (POMs/docs/OpenAPI metadata), build a release candidate, and open a PR against the 3.0.0 branch.
Changes:
- Introduces a
workflow_dispatchGitHub Actions workflow to prepare a 3.0 release PR. - Adds shared Bash release helpers for version validation and artifact existence checks against Maven Central / Sonatype snapshots.
- Adds scripts to bump the project version, generate release notes draft, and update release references across docs/POMs/OpenAPI metadata.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/workflows/prepare-release-3.yml |
Manual workflow to prepare a 3.0.x release branch/PR, validate inputs, build with pinned generators, and open a PR. |
CI/release/common.sh |
Shared Bash helpers for version parsing/validation and Maven artifact probing. |
CI/release/prepare-codegen-release.sh |
Main “prepare release” script: resolves versions, bumps Maven version, drafts release notes, and runs file updates. |
CI/release/update-codegen-release-files.py |
Updates docs/POMs/OpenAPI metadata to reflect the intended release + next snapshot versions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
6e0c79c to
ac4edb7
Compare
daniel-kmiecik
approved these changes
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A manual pre-release workflow for swagger-codegen 3.0 that prepares a release PR against 3.0.0 with validated version inputs and synchronized release file updates.
What’s included
Workflow behavior
Inputs in prepare-release-3
Release version to prepare (e.g. 3.0.80). If empty, derived from current root -SNAPSHOT.
Next dev version after release (e.g. 3.0.81-SNAPSHOT). If empty, auto-incremented from codegen_version.
true/false switch for whether this release is coordinated with generators release flow.
Generators release version to set in codegen when needed (e.g. 1.0.61).
Optional bootstrap version used for dependency-cycle-safe validation/build (can be release or -SNAPSHOT).