Skip to content

Update PR data Monthly collection (2026-02-02T01:55:27Z)#357

Merged
github-actions[bot] merged 1 commit into
mainfrom
auto-update-pr-data
Feb 2, 2026
Merged

Update PR data Monthly collection (2026-02-02T01:55:27Z)#357
github-actions[bot] merged 1 commit into
mainfrom
auto-update-pr-data

Conversation

@gounthar

@gounthar gounthar commented Feb 2, 2026

Copy link
Copy Markdown
Owner

This PR contains automatically updated PR statistics data. Generated by GitHub Actions.

Summary by CodeRabbit

  • New Features

    • Added monthly PR tracking data for January 2026.
  • Updates

    • Refreshed PR statistics and metrics across all consolidated reports, including pull request states, statuses, plugins, and repositories.
    • Updated contributor PR counts to reflect latest activity.

✏️ Tip: You can customize this high-level summary in your review settings.

@github-actions github-actions Bot merged commit 1f563b9 into main Feb 2, 2026
6 of 8 checks passed
@github-actions github-actions Bot deleted the auto-update-pr-data branch February 2, 2026 01:55
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @gounthar, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request provides an automated monthly update to the repository's pull request statistics. It refreshes consolidated data on plugin and repository activity, as well as the overall status and state of PRs. Additionally, it introduces new detailed monthly records for January 2026, ensuring the data remains current.

Highlights

  • Automated Data Update: This pull request automatically updates various JSON data files related to pull request statistics, ensuring the repository's metrics are current.
  • Consolidated Statistics Refresh: Counts for numerous plugins, repositories, and PR states/statuses have been incremented, reflecting recent activity and changes.
  • Monthly Data Addition: New JSON files, 'filtered_prs_2026_01.json' and 'prs_2026_01.json', have been added to include detailed pull request data specifically for January 2026.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai

coderabbitai Bot commented Feb 2, 2026

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

This PR updates consolidated pull request statistics across multiple JSON data files, incrementing plugin and repository counts, adjusting PR state and status distributions, and introducing two new monthly dataset files for January 2026. No code logic or functionality is modified.

Changes

Cohort / File(s) Summary
Consolidated PR Statistics
data/consolidated/prs_by_plugin.json, data/consolidated/prs_by_repo.json
Incremented counts for numerous plugins and repositories by 1; renamed/reassigned several plugin and repository identifiers; introduced new entries including pipeline-npm, send-stacktrace-to-eclipse-plugin, saml, and others. Multiple entry swaps and reorganizations throughout both files.
Aggregated PR States and Statuses
data/consolidated/prs_by_state.json, data/consolidated/prs_by_status.json
Updated PR state counts (OPEN: 423→425, MERGED: 312→362, CLOSED: 53→54); updated status counts (SUCCESS: 403→424, PENDING: 9→41).
User PR Counts
data/consolidated/prs_by_user.json
Updated jonesbusy PR count from 279 to 332.
Monthly PR Datasets
data/monthly/filtered_prs_2026_01.json, data/monthly/prs_2026_01.json
Introduced two new JSON files containing aggregated pull request entries for January 2026, documenting PR metadata (number, title, state, timestamps, user, repository, plugin, labels, status) across Jenkins plugins with automated modernization workflows.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

🐰 The numbers dance, they hop and play,
From twenty-six January's way,
Each plugin count climbs ever higher,
New datasets spark the data fire,
Statistics bloom where PRs blend! 📊

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch auto-update-pr-data

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist gemini-code-assist Bot 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.

Code Review

This pull request is an automated update of PR statistics. The data in the JSON files appears to be updated correctly. However, I've identified an issue with data redundancy. Two new identical files, data/monthly/filtered_prs_2026_01.json and data/monthly/prs_2026_01.json, are being added. This is unnecessary and will increase the repository size over time. I've added a specific comment with a suggestion to improve the data generation process.

Comment on lines +1 to +844
[
{
"number": 31,
"title": "Migrate Commons Lang from 2 to 3",
"state": "CLOSED",
"createdAt": "2026-01-27T07:41:12Z",
"updatedAt": "2026-01-27T07:43:25Z",
"user": "jonesbusy",
"repository": "jenkinsci/filesystem-list-parameter-plugin",
"pluginName": "filesystem-list-parameter-plugin",
"labels": null,
"url": "https://github.com/jenkinsci/filesystem-list-parameter-plugin/pull/31",
"description": "Hello filesystem-list-parameter-plugin developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Migrate Commons Lang from 2 to 3 and StringEscapeUtils to Commons Text\n io.jenkins.tools.pluginmodernizer.MigrateCommonsLang2ToLang3AndCommonText\n Migrate Commons Lang from 2 to 3 and StringEscapeUtils to Commons Text.\n\nThis pull request upgrades Apache Commons Lang 2 to Apache Commons Lang 3. Additionally, if the plugin uses StringEscapeUtils from Apache Commons Lang, it will be migrated to use Apache Commons Text instead.\nThe Apache Commons community recommends using Apache Commons Text for string escaping operations, as it offers a more focused and feature-rich API for text processing.\nWhat's Changed?\n\nMigrated from deprecated/EOL Apache Commons Lang 2 to Commons Lang 3.\nIf applicable: Transitioned from deprecated/EOL StringEscapeUtils in Apache Commons Lang to Commons Text.",
"checkStatus": "PENDING"
},
{
"number": 376,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-27T06:53:15Z",
"updatedAt": "2026-01-27T07:29:14Z",
"user": "jonesbusy",
"repository": "jenkinsci/ansible-plugin",
"pluginName": "ansible",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/ansible-plugin/pull/376",
"description": "Hello ansible developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 15,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-27T06:52:16Z",
"updatedAt": "2026-01-27T07:28:59Z",
"user": "jonesbusy",
"repository": "jenkinsci/exclusive-labels-plugin",
"pluginName": "exclusive-label-plugin",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/exclusive-labels-plugin/pull/15",
"description": "Hello exclusive-label-plugin developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 21,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:58:11Z",
"updatedAt": "2026-01-24T15:00:54Z",
"user": "jonesbusy",
"repository": "jenkinsci/simple-priority-sorter-plugin",
"pluginName": "simple-priority-sorter",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/simple-priority-sorter-plugin/pull/21",
"description": "Hello simple-priority-sorter developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 309,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:56:57Z",
"updatedAt": "2026-01-24T15:00:35Z",
"user": "jonesbusy",
"repository": "jenkinsci/skip-notifications-trait-plugin",
"pluginName": "skip-notifications-trait",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/skip-notifications-trait-plugin/pull/309",
"description": "Hello skip-notifications-trait developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 125,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:55:41Z",
"updatedAt": "2026-01-24T15:00:19Z",
"user": "jonesbusy",
"repository": "jenkinsci/scm-filter-branch-pr-plugin",
"pluginName": "scm-filter-branch-pr",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/scm-filter-branch-pr-plugin/pull/125",
"description": "Hello scm-filter-branch-pr developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 55,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:54:22Z",
"updatedAt": "2026-01-24T14:55:02Z",
"user": "jonesbusy",
"repository": "jenkinsci/s3-jobcacher-storage-plugin",
"pluginName": "s3-jobcacher-storage",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/s3-jobcacher-storage-plugin/pull/55",
"description": "Hello s3-jobcacher-storage developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 401,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:53:00Z",
"updatedAt": "2026-01-24T14:54:42Z",
"user": "jonesbusy",
"repository": "jenkinsci/postgresql-fingerprint-storage-plugin",
"pluginName": "postgresql-fingerprint-storage",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/postgresql-fingerprint-storage-plugin/pull/401",
"description": "Hello postgresql-fingerprint-storage developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 44,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:51:34Z",
"updatedAt": "2026-01-24T14:54:17Z",
"user": "jonesbusy",
"repository": "jenkinsci/pipeline-cps-oras-plugin",
"pluginName": "pipeline-cps-oras",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/pipeline-cps-oras-plugin/pull/44",
"description": "Hello pipeline-cps-oras developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 41,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:50:20Z",
"updatedAt": "2026-01-24T14:54:05Z",
"user": "jonesbusy",
"repository": "jenkinsci/pipeline-lib-oras-plugin",
"pluginName": "pipeline-lib-oras",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/pipeline-lib-oras-plugin/pull/41",
"description": "Hello pipeline-lib-oras developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 253,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:49:04Z",
"updatedAt": "2026-01-24T14:53:54Z",
"user": "jonesbusy",
"repository": "jenkinsci/pipeline-npm-plugin",
"pluginName": "pipeline-npm",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/pipeline-npm-plugin/pull/253",
"description": "Hello pipeline-npm developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 75,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:47:50Z",
"updatedAt": "2026-01-24T14:53:44Z",
"user": "jonesbusy",
"repository": "jenkinsci/pipeline-cps-http-plugin",
"pluginName": "pipeline-cps-http",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/pipeline-cps-http-plugin/pull/75",
"description": "Hello pipeline-cps-http developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 153,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:46:36Z",
"updatedAt": "2026-01-24T14:53:31Z",
"user": "jonesbusy",
"repository": "jenkinsci/parameter-separator-plugin",
"pluginName": "parameter-separator",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/parameter-separator-plugin/pull/153",
"description": "Hello parameter-separator developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 246,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:45:22Z",
"updatedAt": "2026-01-24T14:53:18Z",
"user": "jonesbusy",
"repository": "jenkinsci/oss-symbols-api-plugin",
"pluginName": "oss-symbols-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/oss-symbols-api-plugin/pull/246",
"description": "Hello oss-symbols-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 78,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:44:11Z",
"updatedAt": "2026-01-24T14:53:07Z",
"user": "jonesbusy",
"repository": "jenkinsci/oras-java-api-plugin",
"pluginName": "oras-java-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/oras-java-api-plugin/pull/78",
"description": "Hello oras-java-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 320,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:43:02Z",
"updatedAt": "2026-01-24T14:52:56Z",
"user": "jonesbusy",
"repository": "jenkinsci/openshift-k8s-credentials-plugin",
"pluginName": "openshift-k8s-credentials",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/openshift-k8s-credentials-plugin/pull/320",
"description": "Hello openshift-k8s-credentials developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 179,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:41:47Z",
"updatedAt": "2026-01-24T14:48:13Z",
"user": "jonesbusy",
"repository": "jenkinsci/nunit-plugin",
"pluginName": "nunit",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/nunit-plugin/pull/179",
"description": "Hello nunit developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 213,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:40:33Z",
"updatedAt": "2026-01-24T14:48:24Z",
"user": "jonesbusy",
"repository": "jenkinsci/next-executions-plugin",
"pluginName": "next-executions",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/next-executions-plugin/pull/213",
"description": "Hello next-executions developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 97,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:39:20Z",
"updatedAt": "2026-01-24T14:48:36Z",
"user": "jonesbusy",
"repository": "jenkinsci/mariadb-api-plugin",
"pluginName": "mariadb-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/mariadb-api-plugin/pull/97",
"description": "Hello mariadb-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 169,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:38:12Z",
"updatedAt": "2026-01-24T14:48:48Z",
"user": "jonesbusy",
"repository": "jenkinsci/login-theme-plugin",
"pluginName": "login-theme",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/login-theme-plugin/pull/169",
"description": "Hello login-theme developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 358,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:36:58Z",
"updatedAt": "2026-01-24T14:48:59Z",
"user": "jonesbusy",
"repository": "jenkinsci/locale-plugin",
"pluginName": "locale",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/locale-plugin/pull/358",
"description": "Hello locale developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 44,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:35:44Z",
"updatedAt": "2026-01-24T14:49:12Z",
"user": "jonesbusy",
"repository": "jenkinsci/jsoup-plugin",
"pluginName": "jsoup",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/jsoup-plugin/pull/44",
"description": "Hello jsoup developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 144,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:34:40Z",
"updatedAt": "2026-01-24T14:49:38Z",
"user": "jonesbusy",
"repository": "jenkinsci/jnr-posix-api-plugin",
"pluginName": "jnr-posix-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/jnr-posix-api-plugin/pull/144",
"description": "Hello jnr-posix-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 112,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:33:34Z",
"updatedAt": "2026-01-24T14:49:54Z",
"user": "jonesbusy",
"repository": "jenkinsci/json-path-api-plugin",
"pluginName": "json-path-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/json-path-api-plugin/pull/112",
"description": "Hello json-path-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 105,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:32:28Z",
"updatedAt": "2026-01-24T14:50:03Z",
"user": "jonesbusy",
"repository": "jenkinsci/json-api-plugin",
"pluginName": "json-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/json-api-plugin/pull/105",
"description": "Hello json-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 97,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:31:23Z",
"updatedAt": "2026-01-24T14:50:15Z",
"user": "jonesbusy",
"repository": "jenkinsci/joda-time-api-plugin",
"pluginName": "joda-time-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/joda-time-api-plugin/pull/97",
"description": "Hello joda-time-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 58,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:30:17Z",
"updatedAt": "2026-01-24T14:31:30Z",
"user": "jonesbusy",
"repository": "jenkinsci/jobcacher-oras-storage-plugin",
"pluginName": "jobcacher-oras-storage",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/jobcacher-oras-storage-plugin/pull/58",
"description": "Hello jobcacher-oras-storage developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 124,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:29:02Z",
"updatedAt": "2026-01-24T14:32:03Z",
"user": "jonesbusy",
"repository": "jenkinsci/jobcacher-artifactory-storage-plugin",
"pluginName": "jobcacher-artifactory-storage",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/jobcacher-artifactory-storage-plugin/pull/124",
"description": "Hello jobcacher-artifactory-storage developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 496,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:27:48Z",
"updatedAt": "2026-01-24T14:31:52Z",
"user": "jonesbusy",
"repository": "jenkinsci/jobcacher-plugin",
"pluginName": "jobcacher",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/jobcacher-plugin/pull/496",
"description": "Hello jobcacher developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 48,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:26:26Z",
"updatedAt": "2026-01-24T14:32:26Z",
"user": "jonesbusy",
"repository": "jenkinsci/jcaptcha-plugin",
"pluginName": "jcaptcha-plugin",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/jcaptcha-plugin/pull/48",
"description": "Hello jcaptcha-plugin developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 252,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:24:22Z",
"updatedAt": "2026-01-24T14:33:26Z",
"user": "jonesbusy",
"repository": "jenkinsci/hidden-parameter-plugin",
"pluginName": "hidden-parameter",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/hidden-parameter-plugin/pull/252",
"description": "Hello hidden-parameter developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 25,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:23:09Z",
"updatedAt": "2026-01-24T14:33:37Z",
"user": "jonesbusy",
"repository": "jenkinsci/git-version-monitor-plugin",
"pluginName": "git-version-monitor",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/git-version-monitor-plugin/pull/25",
"description": "Hello git-version-monitor developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 105,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:21:57Z",
"updatedAt": "2026-01-24T14:33:50Z",
"user": "jonesbusy",
"repository": "jenkinsci/gson-api-plugin",
"pluginName": "gson-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/gson-api-plugin/pull/105",
"description": "Hello gson-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 297,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:20:50Z",
"updatedAt": "2026-01-24T14:34:01Z",
"user": "jonesbusy",
"repository": "jenkinsci/gitlab-kubernetes-credentials-plugin",
"pluginName": "gitlab-kubernetes-credentials",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/gitlab-kubernetes-credentials-plugin/pull/297",
"description": "Hello gitlab-kubernetes-credentials developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 148,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:19:33Z",
"updatedAt": "2026-01-24T14:34:12Z",
"user": "jonesbusy",
"repository": "jenkinsci/flyway-runner-plugin",
"pluginName": "flyway-runner",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/flyway-runner-plugin/pull/148",
"description": "Hello flyway-runner developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 232,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:18:13Z",
"updatedAt": "2026-01-24T14:31:10Z",
"user": "jonesbusy",
"repository": "jenkinsci/flyway-api-plugin",
"pluginName": "flyway-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/flyway-api-plugin/pull/232",
"description": "Hello flyway-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 200,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:16:58Z",
"updatedAt": "2026-01-24T14:52:29Z",
"user": "jonesbusy",
"repository": "jenkinsci/file-operations-plugin",
"pluginName": "file-operations",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/file-operations-plugin/pull/200",
"description": "Hello file-operations developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 51,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:15:42Z",
"updatedAt": "2026-01-24T14:52:41Z",
"user": "jonesbusy",
"repository": "jenkinsci/extended-read-permission-plugin",
"pluginName": "extended-read-permission",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/extended-read-permission-plugin/pull/51",
"description": "Hello extended-read-permission developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 187,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:14:14Z",
"updatedAt": "2026-01-24T14:14:59Z",
"user": "jonesbusy",
"repository": "jenkinsci/extra-tool-installers-plugin",
"pluginName": "extra-tool-installers",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/extra-tool-installers-plugin/pull/187",
"description": "Hello extra-tool-installers developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 155,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:12:28Z",
"updatedAt": "2026-01-24T14:13:46Z",
"user": "jonesbusy",
"repository": "jenkinsci/extension-filter-plugin",
"pluginName": "extension-filter",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/extension-filter-plugin/pull/155",
"description": "Hello extension-filter developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 110,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:10:54Z",
"updatedAt": "2026-01-24T14:13:38Z",
"user": "jonesbusy",
"repository": "jenkinsci/database-mariadb-plugin",
"pluginName": "database-mariadb",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/database-mariadb-plugin/pull/110",
"description": "Hello database-mariadb developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 123,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:09:28Z",
"updatedAt": "2026-01-24T14:13:29Z",
"user": "jonesbusy",
"repository": "jenkinsci/coverage-badges-extension-plugin",
"pluginName": "coverage-badges-extension",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/coverage-badges-extension-plugin/pull/123",
"description": "Hello coverage-badges-extension developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 55,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:07:55Z",
"updatedAt": "2026-01-24T14:13:21Z",
"user": "jonesbusy",
"repository": "jenkinsci/commons-math3-api-plugin",
"pluginName": "commons-math3-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/commons-math3-api-plugin/pull/55",
"description": "Hello commons-math3-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 117,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:06:26Z",
"updatedAt": "2026-01-24T14:07:57Z",
"user": "jonesbusy",
"repository": "jenkinsci/byte-buddy-api-plugin",
"pluginName": "byte-buddy-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/byte-buddy-api-plugin/pull/117",
"description": "Hello byte-buddy-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 95,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:05:04Z",
"updatedAt": "2026-01-24T14:07:17Z",
"user": "jonesbusy",
"repository": "jenkinsci/build-history-metrics-plugin",
"pluginName": "build-history-metrics-plugin",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/build-history-metrics-plugin/pull/95",
"description": "Hello build-history-metrics-plugin developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 343,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:03:37Z",
"updatedAt": "2026-01-24T14:06:51Z",
"user": "jonesbusy",
"repository": "jenkinsci/bitbucket-kubernetes-credentials-plugin",
"pluginName": "bitbucket-kubernetes-credentials",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/bitbucket-kubernetes-credentials-plugin/pull/343",
"description": "Hello bitbucket-kubernetes-credentials developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "SUCCESS"
},
{
"number": 88,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T14:01:13Z",
"updatedAt": "2026-01-24T14:06:39Z",
"user": "jonesbusy",
"repository": "jenkinsci/artifactory-client-api-plugin",
"pluginName": "artifactory-client-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/artifactory-client-api-plugin/pull/88",
"description": "Hello artifactory-client-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 150,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T13:59:48Z",
"updatedAt": "2026-01-24T14:06:32Z",
"user": "jonesbusy",
"repository": "jenkinsci/artifactory-artifact-manager-plugin",
"pluginName": "artifactory-artifact-manager",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/artifactory-artifact-manager-plugin/pull/150",
"description": "Hello artifactory-artifact-manager developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 114,
"title": "chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.",
"state": "MERGED",
"createdAt": "2026-01-24T13:56:05Z",
"updatedAt": "2026-01-24T13:57:22Z",
"user": "jonesbusy",
"repository": "jenkinsci/asm-api-plugin",
"pluginName": "asm-api",
"labels": [
"chore"
],
"url": "https://github.com/jenkinsci/asm-api-plugin/pull/114",
"description": "Hello asm-api developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Setup auto-merge workflows\n io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows\n Setup auto-merge workflows for safe dependency updates and bom.\n\nSetup auto-merge workflows\nSetup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).\nWorkflows either merge or close the PRs depending on the dependency.\nWhy is this important?\nReduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.\nClosing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.\nBumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.\nSee Archetype for more details.",
"checkStatus": "PENDING"
},
{
"number": 313,
"title": "Migrate Commons Lang from 2 to 3",
"state": "MERGED",
"createdAt": "2026-01-19T14:19:57Z",
"updatedAt": "2026-01-19T17:08:23Z",
"user": "jonesbusy",
"repository": "jenkinsci/github-oauth-plugin",
"pluginName": "github-oauth",
"labels": [
"enhancement"
],
"url": "https://github.com/jenkinsci/github-oauth-plugin/pull/313",
"description": "Hello github-oauth developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Migrate Commons Lang from 2 to 3 and StringEscapeUtils to Commons Text\n io.jenkins.tools.pluginmodernizer.MigrateCommonsLang2ToLang3AndCommonText\n Migrate Commons Lang from 2 to 3 and StringEscapeUtils to Commons Text.\n\nThis pull request upgrades Apache Commons Lang 2 to Apache Commons Lang 3. Additionally, if the plugin uses StringEscapeUtils from Apache Commons Lang, it will be migrated to use Apache Commons Text instead.\nThe Apache Commons community recommends using Apache Commons Text for string escaping operations, as it offers a more focused and feature-rich API for text processing.\nWhat's Changed?\n\nMigrated from deprecated/EOL Apache Commons Lang 2 to Commons Lang 3.\nIf applicable: Transitioned from deprecated/EOL StringEscapeUtils in Apache Commons Lang to Commons Text.",
"checkStatus": "SUCCESS"
},
{
"number": 159,
"title": "Migrate Commons Lang from 2 to 3",
"state": "MERGED",
"createdAt": "2026-01-19T13:58:09Z",
"updatedAt": "2026-01-19T14:02:17Z",
"user": "jonesbusy",
"repository": "jenkinsci/job-import-plugin",
"pluginName": "job-import-plugin",
"labels": [
"enhancement"
],
"url": "https://github.com/jenkinsci/job-import-plugin/pull/159",
"description": "Hello job-import-plugin developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Migrate Commons Lang from 2 to 3 and StringEscapeUtils to Commons Text\n io.jenkins.tools.pluginmodernizer.MigrateCommonsLang2ToLang3AndCommonText\n Migrate Commons Lang from 2 to 3 and StringEscapeUtils to Commons Text.\n\nThis pull request upgrades Apache Commons Lang 2 to Apache Commons Lang 3. Additionally, if the plugin uses StringEscapeUtils from Apache Commons Lang, it will be migrated to use Apache Commons Text instead.\nThe Apache Commons community recommends using Apache Commons Text for string escaping operations, as it offers a more focused and feature-rich API for text processing.\nWhat's Changed?\n\nMigrated from deprecated/EOL Apache Commons Lang 2 to Commons Lang 3.\nIf applicable: Transitioned from deprecated/EOL StringEscapeUtils in Apache Commons Lang to Commons Text.",
"checkStatus": "PENDING"
},
{
"number": 763,
"title": "Migrate Commons Lang from 2 to 3",
"state": "OPEN",
"createdAt": "2026-01-19T08:05:03Z",
"updatedAt": "2026-01-19T08:05:04Z",
"user": "jonesbusy",
"repository": "jenkinsci/saml-plugin",
"pluginName": "saml",
"labels": null,
"url": "https://github.com/jenkinsci/saml-plugin/pull/763",
"description": "Hello saml developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Migrate Commons Lang from 2 to 3 and StringEscapeUtils to Commons Text\n io.jenkins.tools.pluginmodernizer.MigrateCommonsLang2ToLang3AndCommonText\n Migrate Commons Lang from 2 to 3 and StringEscapeUtils to Commons Text.\n\nThis pull request upgrades Apache Commons Lang 2 to Apache Commons Lang 3. Additionally, if the plugin uses StringEscapeUtils from Apache Commons Lang, it will be migrated to use Apache Commons Text instead.\nThe Apache Commons community recommends using Apache Commons Text for string escaping operations, as it offers a more focused and feature-rich API for text processing.\nWhat's Changed?\n\nMigrated from deprecated/EOL Apache Commons Lang 2 to Commons Lang 3.\nIf applicable: Transitioned from deprecated/EOL StringEscapeUtils in Apache Commons Lang to Commons Text.",
"checkStatus": "SUCCESS"
},
{
"number": 1151,
"title": "Migrate Commons Lang from 2 to 3",
"state": "OPEN",
"createdAt": "2026-01-19T06:58:32Z",
"updatedAt": "2026-01-19T06:58:33Z",
"user": "jonesbusy",
"repository": "jenkinsci/jira-plugin",
"pluginName": "jira",
"labels": null,
"url": "https://github.com/jenkinsci/jira-plugin/pull/1151",
"description": "Hello jira developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Migrate Commons Lang from 2 to 3 and StringEscapeUtils to Commons Text\n io.jenkins.tools.pluginmodernizer.MigrateCommonsLang2ToLang3AndCommonText\n Migrate Commons Lang from 2 to 3 and StringEscapeUtils to Commons Text.\n\nThis pull request upgrades Apache Commons Lang 2 to Apache Commons Lang 3. Additionally, if the plugin uses StringEscapeUtils from Apache Commons Lang, it will be migrated to use Apache Commons Text instead.\nThe Apache Commons community recommends using Apache Commons Text for string escaping operations, as it offers a more focused and feature-rich API for text processing.\nWhat's Changed?\n\nMigrated from deprecated/EOL Apache Commons Lang 2 to Commons Lang 3.\nIf applicable: Transitioned from deprecated/EOL StringEscapeUtils in Apache Commons Lang to Commons Text.",
"checkStatus": "SUCCESS"
}
]

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.

medium

This file is identical to data/monthly/prs_2026_01.json. Committing two identical files leads to data duplication and increases the repository size unnecessarily. It appears the generation script creates this file as a copy of the other. Consider modifying the script to use a single file for subsequent processing steps to avoid this redundancy. For instance, if this file is an intermediate step, it could be generated, used, and then removed within the script without being committed to the repository.

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.

1 participant