Merge branch 'master' into enable-top-button-for-heterolist

Author: mawinter69

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,17 +1,24 @@
+<!-- Comment:
+!!! ⚠️ IMPORTANT ⚠️ !!!
+Do not remove any of the sections below, even if they are not applicable to your change. The sections are used by the
+changelog generator and other tools to extract information about the change. If a section is not applicable,
+leave as is. Carefully read the instructions in each section and provide the necessary information.
+
+Pull requests that do not follow the template might be closed without further review.
+-->
+
 <!-- Comment:
 A great PR typically begins with the line below.
-Replace XXXXX with the numeric part of the issue ID you created in Jira.
-Note that if you want your changes backported into LTS, you need to create a Jira issue. See https://www.jenkins.io/download/lts/#backporting-process for more information.
+Replace <issue-number> with the issue number.
 -->
 
-See [JENKINS-XXXXX](https://issues.jenkins.io/browse/JENKINS-XXXXX).
+Fixes #<issue-number>
 
 <!-- Comment:
-If the issue is not fully described in Jira, add more information here (justification, pull request links, etc.).
+If the issue is not fully described in the issue tracker, add more information here (justification, pull request links, etc.).
 
- * We do not require Jira issues for minor improvements.
- * Bug fixes should have a Jira issue to facilitate the backporting process.
- * Major new features should have a Jira issue.
+ * We do not require an issue for minor improvements.
+ * Major new features should have an issue created.
 -->
 
 ### Testing done
@@ -26,6 +33,16 @@ For frontend changes, include screenshots of the relevant page(s) before and aft
 For refactoring and code cleanup changes, exercise the code before and after the change and verify the behavior remains the same.
 -->
 
+### Screenshots (UI changes only)
+
+<!--
+If your change involves a UI change, please include screenshots showing the before and after states.
+-->
+
+#### Before
+
+#### After
+
 ### Proposed changelog entries
 
 - human-readable text
@@ -34,8 +51,8 @@ For refactoring and code cleanup changes, exercise the code before and after the
 The changelog entry should be in the imperative mood; e.g., write "do this"/"return that" rather than "does this"/"returns that".
 For examples, see: https://www.jenkins.io/changelog/
 
-Do not include the Jira issue in the changelog entry.
-Include the Jira issue in the description of the pull request so that the changelog generator can find it and include it in the generated changelog.
+Do not include the issue in the changelog entry.
+Include the issue in the description of the pull request so that the changelog generator can find it and include it in the generated changelog.
 
 You may add multiple changelog entries if applicable by adding a new entry to the list, e.g.
 - First changelog entry
@@ -82,7 +99,7 @@ The changelog generator relies on the presence of the upgrade guidelines section
 
 ### Submitter checklist
 
-- [ ] The Jira issue, if it exists, is well-described.
+- [ ] The issue, if it exists, is well-described.
 - [ ] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see [examples](https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs/weekly.yml)). Fill in the **Proposed upgrade guidelines** section only if there are breaking changes or changes that may require extra steps from users during upgrade.
 - [ ] There is automated testing or an explanation as to why this change has no tests.
 - [ ] New public classes, fields, and methods are annotated with `@Restricted` or have `@since TODO` Javadocs, as appropriate.
@@ -108,4 +125,4 @@ Before the changes are marked as `ready-for-merge`:
 - [ ] Changelog entries in the pull request title and/or **Proposed changelog entries** are accurate, human-readable, and in the imperative mood.
 - [ ] Proper changelog labels are set so that the changelog can be generated automatically.
 - [ ] If the change needs additional upgrade steps from users, the `upgrade-guide-needed` label is set and there is a **Proposed upgrade guidelines** section in the pull request title (see [example](https://github.com/jenkinsci/jenkins/pull/4387)).
-- [ ] If it would make sense to backport the change to LTS, a Jira issue must exist, be a _Bug_ or _Improvement_, and be labeled as `lts-candidate` to be considered (see [query](https://issues.jenkins.io/issues/?filter=12146)).
+- [ ] If it would make sense to backport the change to LTS, be a _Bug_ or _Improvement_, and either the issue or pull request must be labeled as `lts-candidate` to be considered.

.github/renovate.json

@@ -1,33 +1,12 @@
 {
   "$schema": "https://docs.renovatebot.com/renovate-schema.json",
-  "extends": [
-    "config:recommended",
-    ":disableDependencyDashboard",
-    ":semanticCommitsDisabled"
-  ],
+  "extends": ["github>jenkinsci/renovate-config", "schedule:daily"],
   "prHourlyLimit": 0,
   "prConcurrentLimit": 0,
-  "postUpdateOptions": [
-    "yarnDedupeHighest"
-  ],
   "packageRules": [
-    {
-      "matchDatasources": [
-        "npm"
-      ],
-      "addLabels": [
-        "javascript"
-      ],
-      "minimumReleaseAge": "3 days",
-      "reviewers": [
-        "team:sig-ux"
-      ]
-    },
     {
       "description": "Should be upgraded in lockstep in order to keep their corresponding Jetty versions aligned",
-      "matchManagers": [
-        "maven"
-      ],
+      "matchManagers": ["maven"],
       "groupName": "Winstone and Jetty",
       "matchPackageNames": [
         "org.eclipse.jetty.ee9:jetty-ee9-maven-plugin",
@@ -36,9 +15,7 @@
     },
     {
       "description": "Provided by Jetty and should be aligned with the version provided by the version of Jetty we deliver. See: https://github.com/jenkinsci/jenkins/pull/5211",
-      "matchManagers": [
-        "maven"
-      ],
+      "matchManagers": ["maven"],
       "enabled": false,
       "matchPackageNames": [
         "jakarta.servlet:jakarta.servlet-api",
@@ -47,148 +24,78 @@
     },
     {
       "description": "Needs significant testing. See: https://github.com/jenkinsci/jenkins/pull/5112#issuecomment-744429487 and https://github.com/jenkinsci/jenkins/pull/5116#issuecomment-744526638",
-      "matchManagers": [
-        "maven"
-      ],
+      "matchManagers": ["maven"],
       "allowedVersions": "<2.5.0",
-      "matchPackageNames": [
-        "org.codehaus.groovy:groovy-all"
-      ]
+      "matchPackageNames": ["org.codehaus.groovy:groovy-all"]
     },
     {
       "description": "Consumed by Groovy and should be updated in lockstep with Groovy. See: https://github.com/jenkinsci/jenkins/pull/5184",
-      "matchManagers": [
-        "maven"
-      ],
+      "matchManagers": ["maven"],
       "enabled": false,
-      "matchPackageNames": [
-        "org.fusesource.jansi:jansi"
-      ]
+      "matchPackageNames": ["org.fusesource.jansi:jansi"]
     },
     {
       "description": "Contains incompatible API changes and needs compatibility work. See: https://github.com/jenkinsci/jenkins/pull/4224",
-      "matchManagers": [
-        "maven"
-      ],
+      "matchManagers": ["maven"],
       "enabled": false,
-      "matchPackageNames": [
-        "org.jfree:jfreechart"
-      ]
+      "matchPackageNames": ["org.jfree:jfreechart"]
     },
     {
       "description": "Starting with 7.x, Guice switches from javax.* to jakarta.* bindings. See https://github.com/google/guice/wiki/Guice700",
-      "matchManagers": [
-        "maven"
-      ],
+      "matchManagers": ["maven"],
       "allowedVersions": "<7.0.0",
-      "matchPackageNames": [
-        "com.google.inject:guice-bom"
-      ]
+      "matchPackageNames": ["com.google.inject:guice-bom"]
     },
     {
-      "matchFileNames": [
-        "core/pom.xml",
-        "test/pom.xml",
-        "war/pom.xml"
-      ],
-      "matchPackageNames": [
-        "org.jenkins-ci.main:remoting"
-      ],
+      "matchFileNames": ["core/pom.xml", "test/pom.xml", "war/pom.xml"],
+      "matchPackageNames": ["org.jenkins-ci.main:remoting"],
       "description": "Avoid updating the remoting.minimum.supported.version property but still update latest one by not placing this property in the parent pom.xml",
       "enabled": false
     },
     {
-      "matchPackageNames": [
-        "net.jcip:jcip-annotations"
-      ],
-      "matchDatasources": [
-        "maven"
-      ],
+      "matchPackageNames": ["net.jcip:jcip-annotations"],
+      "matchDatasources": ["maven"],
       "enabled": false,
       "description": "maven-metadata.xml is missing for this really old package which is required by renovate"
     }
   ],
   "customManagers": [
     {
       "customType": "regex",
-      "fileMatch": [
-        "pom.xml"
-      ],
-      "matchStrings": [
-        "<node.version>(?<currentValue>.*?)</node.version>"
-      ],
+      "managerFilePatterns": ["/pom.xml/"],
+      "matchStrings": ["<node.version>(?<currentValue>.*?)</node.version>"],
       "depNameTemplate": "node",
       "datasourceTemplate": "node-version"
     },
     {
       "customType": "regex",
-      "fileMatch": [
-        "ath.sh"
-      ],
-      "matchStrings": [
-        "export ATH_VERSION=(?<currentValue>.*?)\n"
-      ],
+      "managerFilePatterns": ["/ath.sh/"],
+      "matchStrings": ["export ATH_VERSION=(?<currentValue>.*?)\n"],
       "depNameTemplate": "jenkins/ath",
       "datasourceTemplate": "docker",
       "versioningTemplate": "loose"
     },
     {
       "customType": "regex",
-      "fileMatch": [
-        ".gitpod/Dockerfile"
-      ],
-      "matchStrings": [
-        "ARG MAVEN_VERSION=(?<currentValue>.*?)\n"
-      ],
-      "depNameTemplate": "org.apache.maven:maven-core",
-      "datasourceTemplate": "maven"
-    },
-    {
-      "customType": "regex",
-      "fileMatch": [
-        "core/src/site/site.xml"
-      ],
-      "matchStrings": [
-        "lit@(?<currentValue>.*?)/"
-      ],
+      "managerFilePatterns": ["/core/src/site/site.xml/"],
+      "matchStrings": ["lit@(?<currentValue>.*?)/"],
       "depNameTemplate": "lit",
       "datasourceTemplate": "npm"
     },
     {
       "customType": "regex",
-      "fileMatch": [
-        "core/src/site/site.xml"
-      ],
-      "matchStrings": [
-        "webcomponentsjs@(?<currentValue>.*?)/"
-      ],
+      "managerFilePatterns": ["/core/src/site/site.xml/"],
+      "matchStrings": ["webcomponentsjs@(?<currentValue>.*?)/"],
       "depNameTemplate": "@webcomponents/webcomponentsjs",
       "datasourceTemplate": "npm"
     },
     {
       "customType": "regex",
-      "fileMatch": [
-        "core/src/site/site.xml"
-      ],
-      "matchStrings": [
-        "<version>(?<currentValue>.*?)</version>"
-      ],
+      "managerFilePatterns": ["/core/src/site/site.xml/"],
+      "matchStrings": ["<version>(?<currentValue>.*?)</version>"],
       "depNameTemplate": "org.apache.maven.skins:maven-fluido-skin",
       "datasourceTemplate": "maven"
     }
   ],
-  "labels": [
-    "dependencies",
-    "skip-changelog"
-  ],
-  "rebaseWhen": "conflicted",
-  "ignorePaths": [
-    "**/node_modules/**",
-    "**/bower_components/**",
-    "**/vendor/**",
-    "**/examples/**",
-    "**/__tests__/**",
-    "**/tests/**",
-    "**/__fixtures__/**"
-  ]
+  "labels": ["dependencies", "skip-changelog"]
 }

.github/workflows/announce-lts-rc.yml

@@ -17,7 +17,7 @@ jobs:
           discourse-author-username: jenkins-release-bot
           discourse-category: 23
       - name: Post on mailing list
-        uses: dawidd6/action-send-mail@6d98ae34d733f9a723a9e04e94f2f24ba05e1402 # v6
+        uses: dawidd6/action-send-mail@62a2d05b79935ad4fb90ce9079928099579c14ac # v9
         with:
           server_address: smtp.gmail.com
           server_port: 465

.github/workflows/changelog.yml

@@ -24,7 +24,7 @@ jobs:
       # Drafts your next Release notes as Pull Requests are merged into "master"
       - name: Generate GitHub Release Draft
         id: release-drafter
-        uses: release-drafter/release-drafter@b1476f6e6eb133afa41ed8589daba6dc69b4d3f5 # v6.1.0
+        uses: release-drafter/release-drafter@6db134d15f3909ccc9eefd369f02bd1e9cffdf97 # v6.2.0
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
       # Generates a YAML changelog file using https://github.com/jenkinsci/jenkins-core-changelog-generator
@@ -35,7 +35,7 @@ jobs:
         env:
           GITHUB_AUTH: github-actions:${{ secrets.GITHUB_TOKEN }}
       - name: Upload Changelog YAML
-        uses: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4 # v5.0.0
+        uses: actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f # v6.0.0
         with:
           name: changelog.yaml
           path: changelog.yaml
@@ -44,15 +44,15 @@ jobs:
     runs-on: ubuntu-latest
     if: github.repository_owner == 'jenkinsci'
     steps:
-      - uses: actions/create-github-app-token@67018539274d69449ef7c02e8e71183d1719ab42 # v2.1.4
+      - uses: actions/create-github-app-token@29824e69f54612133e76f7eaac726eef6c875baf # v2.2.1
         id: generate-token
         with:
           app-id: ${{ secrets.JENKINS_CHANGELOG_UPDATER_APP_ID }}
           private-key: ${{ secrets.JENKINS_CHANGELOG_UPDATER_PRIVATE_KEY }}
           owner: jenkins-infra
           repositories: jenkins.io
       - name: Check out
-        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
         with:
           fetch-depth: 0
       - name: Publish jenkins.io changelog draft