Skip to content

Conversation

basil
Copy link
Member

@basil basil commented Jul 30, 2025

No need to use a third-party library when this functionality is available in the Java Platform.

@basil basil added the internal label Jul 30, 2025
@basil basil requested a review from a team as a code owner July 30, 2025 15:19
Copy link
Member

@alecharp alecharp left a comment

Choose a reason for hiding this comment

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

Sounds good to me.

@alecharp alecharp added this pull request to the merge queue Jul 30, 2025
@basil basil removed this pull request from the merge queue due to a manual request Jul 30, 2025
@basil basil merged commit d788654 into jenkinsci:master Jul 30, 2025
17 checks passed
@alecharp
Copy link
Member

Adding developer to trigger a release.

@jglick
Copy link
Member

jglick commented Jul 31, 2025

@alecharp that does not take effect retroactively; you can manually trigger a release using GH Actions UI if you need to.

@alecharp
Copy link
Member

alecharp commented Jul 31, 2025 via email

@jglick
Copy link
Member

jglick commented Jul 31, 2025

Yes, I am just saying that the choice of label has no effect at that point except to control the appearance of the release notes Markdown; it does not cause the release to be triggered after the master workflow runs in response to the passing CI build of the merge commit.

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

Successfully merging this pull request may close these issues.

3 participants