Skip to content

chore: update 1.x workflow#2366

Closed
zepfred wants to merge 1 commit into
TimefoldAI:mainfrom
zepfred:chore/update-release-1.x-2
Closed

chore: update 1.x workflow#2366
zepfred wants to merge 1 commit into
TimefoldAI:mainfrom
zepfred:chore/update-release-1.x-2

Conversation

@zepfred

@zepfred zepfred commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

No description provided.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the 1.x release automation to run JReleaser with an explicit, dedicated configuration file, aiming to standardize/reproduce the Maven Central + GitHub release process for 1.x releases.

Changes:

  • Added a new jreleaser-1.x.yml configuration describing signing, GitHub release, changelog formatting, and Maven Central publishing details for 1.x releases.
  • Updated the release-1.x GitHub Actions workflow to pass full-release --config-file jreleaser-1.x.yml to the JReleaser action.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
jreleaser-1.x.yml Introduces a dedicated JReleaser configuration for the 1.x release pipeline (GitHub release + Maven Central publish).
.github/workflows/release-1.x.yml Configures the JReleaser action invocation to use the new 1.x config file.

Comment on lines +102 to +103
with:
arguments: full-release --config-file jreleaser-1.x.yml
@zepfred

zepfred commented Jun 12, 2026

Copy link
Copy Markdown
Contributor Author

Thinking about this workflow, I believe we won't need the file on the main branch, since we will check out the 1.x branch, which contains it.

@zepfred zepfred closed this Jun 12, 2026
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants