Update PR data Monthly collection (2025-11-02T01:22:27Z) #240
Conversation
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
Contributor
|
Caution Review failedThe pull request is closed. WalkthroughThis PR updates Jenkins plugin statistics and PR metrics data by reorganizing plugin rankings across multiple consolidated data files, updating PR state/status counts, and introducing new monthly PR records for October 2025. Changes include substantial plugin name remappings, count adjustments, and additions of new monthly filtered data. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes
Possibly related PRs
Poem
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (8)
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. Comment |
Contributor
Summary of ChangesHello @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 serves to automatically update the repository's pull request statistics. It refreshes the consolidated data files that track PRs by plugin, repository, state, status, and user, ensuring these metrics are current. Additionally, it introduces new monthly data files for October 2025, providing a detailed snapshot of PR activity for that period. This automated process, driven by GitHub Actions, helps maintain up-to-date insights into development trends and contributions. Highlights
Using Gemini Code AssistThe 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
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 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
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request is an automated update of PR statistics data. It correctly updates several consolidated data files and adds new monthly data. However, I've identified an issue with data redundancy in the newly added files. Specifically, three identical files for October 2025 data have been added: prs_2025_10.json, filtered_prs_2025_10.json, and prs_2025_10.json.partial. This is unnecessary and can lead to confusion. The filename filtered_prs_2025_10.json is misleading, as it's a copy of the raw data, not a filtered version. The file prs_2025_10.json.partial appears to be a temporary file that should have been removed after processing. I've left specific comments on the redundant files. Fixing the underlying script to avoid committing these duplicate files would improve the data collection process.
Comment on lines
+1
to
+386
| [ | ||
| { | ||
| "number": 2, | ||
| "title": "chore(pom): Use recommended core version 2.504.3, and Java 11", | ||
| "state": "CLOSED", | ||
| "createdAt": "2025-10-31T15:55:29Z", | ||
| "updatedAt": "2025-10-31T16:05:57Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/simple-priority-sorter-plugin", | ||
| "pluginName": "simple-priority-sorter", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/simple-priority-sorter-plugin/pull/2", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 289, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:53:05Z", | ||
| "updatedAt": "2025-10-31T16:05:20Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/skip-notifications-trait-plugin", | ||
| "pluginName": "skip-notifications-trait", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/skip-notifications-trait-plugin/pull/289", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 41, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:50:21Z", | ||
| "updatedAt": "2025-10-31T16:04:11Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/s3-jobcacher-storage-plugin", | ||
| "pluginName": "s3-jobcacher-storage", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/s3-jobcacher-storage-plugin/pull/41", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 387, | ||
| "title": "chore(pom): Use recommended core version 2.504.3, and Java 11", | ||
| "state": "OPEN", | ||
| "createdAt": "2025-10-31T15:45:30Z", | ||
| "updatedAt": "2025-10-31T16:09:39Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/postgresql-fingerprint-storage-plugin", | ||
| "pluginName": "postgresql-fingerprint-storage", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/postgresql-fingerprint-storage-plugin/pull/387", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "FAILURE" | ||
| }, | ||
| { | ||
| "number": 27, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:43:22Z", | ||
| "updatedAt": "2025-10-31T16:00:40Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/pipeline-cps-oras-plugin", | ||
| "pluginName": "pipeline-cps-oras", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/pipeline-cps-oras-plugin/pull/27", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 23, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:40:36Z", | ||
| "updatedAt": "2025-10-31T16:00:56Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/pipeline-lib-oras-plugin", | ||
| "pluginName": "pipeline-lib-oras", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/pipeline-lib-oras-plugin/pull/23", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 233, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:37:52Z", | ||
| "updatedAt": "2025-10-31T16:01:45Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/pipeline-npm-plugin", | ||
| "pluginName": "pipeline-npm", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/pipeline-npm-plugin/pull/233", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 300, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "CLOSED", | ||
| "createdAt": "2025-10-31T15:31:59Z", | ||
| "updatedAt": "2025-10-31T16:02:00Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/openshift-k8s-credentials-plugin", | ||
| "pluginName": "openshift-k8s-credentials", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/openshift-k8s-credentials-plugin/pull/300", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 186, | ||
| "title": "chore(pom): Use recommended core version 2.504.3, and Java 11", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:28:09Z", | ||
| "updatedAt": "2025-10-31T16:02:34Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/next-executions-plugin", | ||
| "pluginName": "next-executions", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/next-executions-plugin/pull/186", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 338, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:24:13Z", | ||
| "updatedAt": "2025-10-31T16:02:54Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/locale-plugin", | ||
| "pluginName": "locale", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/locale-plugin/pull/338", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 192, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:21:41Z", | ||
| "updatedAt": "2025-10-31T16:03:19Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/junit-attachments-plugin", | ||
| "pluginName": "junit-attachments", | ||
| "labels": [ | ||
| "dependencies" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/junit-attachments-plugin/pull/192", | ||
| "description": "Hello junit-attachments 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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 42, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:18:34Z", | ||
| "updatedAt": "2025-10-31T15:28:10Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/jobcacher-oras-storage-plugin", | ||
| "pluginName": "jobcacher-oras-storage", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/jobcacher-oras-storage-plugin/pull/42", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 112, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:15:44Z", | ||
| "updatedAt": "2025-10-31T15:27:48Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/jobcacher-artifactory-storage-plugin", | ||
| "pluginName": "jobcacher-artifactory-storage", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/jobcacher-artifactory-storage-plugin/pull/112", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 463, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:13:02Z", | ||
| "updatedAt": "2025-10-31T16:03:43Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/jobcacher-plugin", | ||
| "pluginName": "jobcacher", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/jobcacher-plugin/pull/463", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 30, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:07:36Z", | ||
| "updatedAt": "2025-10-31T15:24:43Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/jcaptcha-plugin", | ||
| "pluginName": "jcaptcha-plugin", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/jcaptcha-plugin/pull/30", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 236, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:05:46Z", | ||
| "updatedAt": "2025-10-31T15:24:59Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/hidden-parameter-plugin", | ||
| "pluginName": "hidden-parameter", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/hidden-parameter-plugin/pull/236", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 273, | ||
| "title": "chore(pom): Use recommended core version 2.504.3, and Java 11", | ||
| "state": "OPEN", | ||
| "createdAt": "2025-10-31T15:02:46Z", | ||
| "updatedAt": "2025-10-31T15:02:48Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/gitlab-kubernetes-credentials-plugin", | ||
| "pluginName": "gitlab-kubernetes-credentials", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/gitlab-kubernetes-credentials-plugin/pull/273", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "FAILURE" | ||
| }, | ||
| { | ||
| "number": 171, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:56:28Z", | ||
| "updatedAt": "2025-10-31T15:25:08Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/extra-tool-installers-plugin", | ||
| "pluginName": "extra-tool-installers", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/extra-tool-installers-plugin/pull/171", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 141, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:53:33Z", | ||
| "updatedAt": "2025-10-31T15:25:41Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/extension-filter-plugin", | ||
| "pluginName": "extension-filter", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/extension-filter-plugin/pull/141", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 96, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:51:13Z", | ||
| "updatedAt": "2025-10-31T15:25:50Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/database-mariadb-plugin", | ||
| "pluginName": "database-mariadb", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/database-mariadb-plugin/pull/96", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 109, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:48:35Z", | ||
| "updatedAt": "2025-10-31T15:25:56Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/coverage-badges-extension-plugin", | ||
| "pluginName": "coverage-badges-extension", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/coverage-badges-extension-plugin/pull/109", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 81, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:45:39Z", | ||
| "updatedAt": "2025-10-31T15:26:06Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/build-history-metrics-plugin", | ||
| "pluginName": "build-history-metrics-plugin", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/build-history-metrics-plugin/pull/81", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 323, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:43:08Z", | ||
| "updatedAt": "2025-10-31T15:27:14Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/bitbucket-kubernetes-credentials-plugin", | ||
| "pluginName": "bitbucket-kubernetes-credentials", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/bitbucket-kubernetes-credentials-plugin/pull/323", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 133, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:40:16Z", | ||
| "updatedAt": "2025-10-31T15:27:07Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/artifactory-artifact-manager-plugin", | ||
| "pluginName": "artifactory-artifact-manager", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/artifactory-artifact-manager-plugin/pull/133", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| } | ||
| ] |
Contributor
There was a problem hiding this comment.
This file is identical to data/monthly/prs_2025_10.json. The filename filtered_prs... suggests it should contain a filtered subset of data, but it's currently a full copy. This is misleading and could cause confusion for anyone using this data. It's recommended to update the generation script to either perform the intended filtering or remove this redundant file to improve maintainability.
Comment on lines
+1
to
+386
| [ | ||
| { | ||
| "number": 2, | ||
| "title": "chore(pom): Use recommended core version 2.504.3, and Java 11", | ||
| "state": "CLOSED", | ||
| "createdAt": "2025-10-31T15:55:29Z", | ||
| "updatedAt": "2025-10-31T16:05:57Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/simple-priority-sorter-plugin", | ||
| "pluginName": "simple-priority-sorter", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/simple-priority-sorter-plugin/pull/2", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 289, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:53:05Z", | ||
| "updatedAt": "2025-10-31T16:05:20Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/skip-notifications-trait-plugin", | ||
| "pluginName": "skip-notifications-trait", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/skip-notifications-trait-plugin/pull/289", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 41, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:50:21Z", | ||
| "updatedAt": "2025-10-31T16:04:11Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/s3-jobcacher-storage-plugin", | ||
| "pluginName": "s3-jobcacher-storage", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/s3-jobcacher-storage-plugin/pull/41", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 387, | ||
| "title": "chore(pom): Use recommended core version 2.504.3, and Java 11", | ||
| "state": "OPEN", | ||
| "createdAt": "2025-10-31T15:45:30Z", | ||
| "updatedAt": "2025-10-31T16:09:39Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/postgresql-fingerprint-storage-plugin", | ||
| "pluginName": "postgresql-fingerprint-storage", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/postgresql-fingerprint-storage-plugin/pull/387", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "FAILURE" | ||
| }, | ||
| { | ||
| "number": 27, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:43:22Z", | ||
| "updatedAt": "2025-10-31T16:00:40Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/pipeline-cps-oras-plugin", | ||
| "pluginName": "pipeline-cps-oras", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/pipeline-cps-oras-plugin/pull/27", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 23, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:40:36Z", | ||
| "updatedAt": "2025-10-31T16:00:56Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/pipeline-lib-oras-plugin", | ||
| "pluginName": "pipeline-lib-oras", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/pipeline-lib-oras-plugin/pull/23", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 233, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:37:52Z", | ||
| "updatedAt": "2025-10-31T16:01:45Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/pipeline-npm-plugin", | ||
| "pluginName": "pipeline-npm", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/pipeline-npm-plugin/pull/233", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 300, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "CLOSED", | ||
| "createdAt": "2025-10-31T15:31:59Z", | ||
| "updatedAt": "2025-10-31T16:02:00Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/openshift-k8s-credentials-plugin", | ||
| "pluginName": "openshift-k8s-credentials", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/openshift-k8s-credentials-plugin/pull/300", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 186, | ||
| "title": "chore(pom): Use recommended core version 2.504.3, and Java 11", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:28:09Z", | ||
| "updatedAt": "2025-10-31T16:02:34Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/next-executions-plugin", | ||
| "pluginName": "next-executions", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/next-executions-plugin/pull/186", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 338, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:24:13Z", | ||
| "updatedAt": "2025-10-31T16:02:54Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/locale-plugin", | ||
| "pluginName": "locale", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/locale-plugin/pull/338", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 192, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:21:41Z", | ||
| "updatedAt": "2025-10-31T16:03:19Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/junit-attachments-plugin", | ||
| "pluginName": "junit-attachments", | ||
| "labels": [ | ||
| "dependencies" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/junit-attachments-plugin/pull/192", | ||
| "description": "Hello junit-attachments 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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 42, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:18:34Z", | ||
| "updatedAt": "2025-10-31T15:28:10Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/jobcacher-oras-storage-plugin", | ||
| "pluginName": "jobcacher-oras-storage", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/jobcacher-oras-storage-plugin/pull/42", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 112, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:15:44Z", | ||
| "updatedAt": "2025-10-31T15:27:48Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/jobcacher-artifactory-storage-plugin", | ||
| "pluginName": "jobcacher-artifactory-storage", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/jobcacher-artifactory-storage-plugin/pull/112", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 463, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:13:02Z", | ||
| "updatedAt": "2025-10-31T16:03:43Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/jobcacher-plugin", | ||
| "pluginName": "jobcacher", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/jobcacher-plugin/pull/463", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 30, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:07:36Z", | ||
| "updatedAt": "2025-10-31T15:24:43Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/jcaptcha-plugin", | ||
| "pluginName": "jcaptcha-plugin", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/jcaptcha-plugin/pull/30", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 236, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T15:05:46Z", | ||
| "updatedAt": "2025-10-31T15:24:59Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/hidden-parameter-plugin", | ||
| "pluginName": "hidden-parameter", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/hidden-parameter-plugin/pull/236", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 273, | ||
| "title": "chore(pom): Use recommended core version 2.504.3, and Java 11", | ||
| "state": "OPEN", | ||
| "createdAt": "2025-10-31T15:02:46Z", | ||
| "updatedAt": "2025-10-31T15:02:48Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/gitlab-kubernetes-credentials-plugin", | ||
| "pluginName": "gitlab-kubernetes-credentials", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/gitlab-kubernetes-credentials-plugin/pull/273", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "FAILURE" | ||
| }, | ||
| { | ||
| "number": 171, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:56:28Z", | ||
| "updatedAt": "2025-10-31T15:25:08Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/extra-tool-installers-plugin", | ||
| "pluginName": "extra-tool-installers", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/extra-tool-installers-plugin/pull/171", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 141, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:53:33Z", | ||
| "updatedAt": "2025-10-31T15:25:41Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/extension-filter-plugin", | ||
| "pluginName": "extension-filter", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/extension-filter-plugin/pull/141", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 96, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:51:13Z", | ||
| "updatedAt": "2025-10-31T15:25:50Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/database-mariadb-plugin", | ||
| "pluginName": "database-mariadb", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/database-mariadb-plugin/pull/96", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 109, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:48:35Z", | ||
| "updatedAt": "2025-10-31T15:25:56Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/coverage-badges-extension-plugin", | ||
| "pluginName": "coverage-badges-extension", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/coverage-badges-extension-plugin/pull/109", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 81, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:45:39Z", | ||
| "updatedAt": "2025-10-31T15:26:06Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/build-history-metrics-plugin", | ||
| "pluginName": "build-history-metrics-plugin", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/build-history-metrics-plugin/pull/81", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 323, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:43:08Z", | ||
| "updatedAt": "2025-10-31T15:27:14Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/bitbucket-kubernetes-credentials-plugin", | ||
| "pluginName": "bitbucket-kubernetes-credentials", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/bitbucket-kubernetes-credentials-plugin/pull/323", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| }, | ||
| { | ||
| "number": 133, | ||
| "title": "chore(pom): Use recommended core version 2.504.3", | ||
| "state": "MERGED", | ||
| "createdAt": "2025-10-31T14:40:16Z", | ||
| "updatedAt": "2025-10-31T15:27:07Z", | ||
| "user": "jonesbusy", | ||
| "repository": "jenkinsci/artifactory-artifact-manager-plugin", | ||
| "pluginName": "artifactory-artifact-manager", | ||
| "labels": [ | ||
| "developer" | ||
| ], | ||
| "url": "https://github.com/jenkinsci/artifactory-artifact-manager-plugin/pull/133", | ||
| "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 Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.504.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.504.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "SUCCESS" | ||
| } | ||
| ] |
Contributor
There was a problem hiding this comment.
This file appears to be a duplicate of data/monthly/prs_2025_10.json and data/monthly/filtered_prs_2025_10.json. The .partial extension suggests it might be a temporary file that was unintentionally committed. Committing such files increases repository size and can lead to maintenance issues. Please ensure that temporary files are cleaned up and not included in commits.
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.
This PR contains automatically updated PR statistics data. Generated by GitHub Actions.
Summary by CodeRabbit