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

chore(sample-plugin): Bump the LTS to 2.492.3. #4830

Merged
merged 1 commit into from
Apr 2, 2025
Merged

Conversation

gounthar
Copy link
Contributor

@gounthar gounthar commented Apr 2, 2025

Update the jenkins.version in the most recent release profile in plugin BOM to the newly released version (cf jenkins-infra/release#664).

Testing done

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

@gounthar gounthar requested a review from a team as a code owner April 2, 2025 16:04
@@ -1698,7 +1698,7 @@
<id>2.492.x</id>
<properties>
<bom>2.492.x</bom>
<jenkins.version>2.492.2</jenkins.version>
<jenkins.version>2.492.3</jenkins.version>
Copy link
Member

@krisstern krisstern Apr 2, 2025

Choose a reason for hiding this comment

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

Is 2.492 considered the active or previous line? I have a feeling this is supposed to be 2.492.1 still...

Copy link
Member

Choose a reason for hiding this comment

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

I think we are supposed to update this after the next .1 release

Copy link
Member

Choose a reason for hiding this comment

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

But given we just have a security release yeah we should update this now.

@krisstern krisstern enabled auto-merge April 2, 2025 16:16
@krisstern krisstern merged commit 83921de into master Apr 2, 2025
5 of 6 checks passed
@krisstern krisstern deleted the gounthar-patch-1 branch April 2, 2025 16:31
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