Merge branch 'main' into topic/renovate-authors

.changeset/forty-beds-bow.md

@@ -0,0 +1,5 @@
+---
+'@backstage-community/plugins': patch
+---
+
+Adding emitting analytics event for removing shortcut.

.editorconfig

@@ -0,0 +1,31 @@
+# EditorConfig is awesome: https://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+end_of_line = lf
+insert_final_newline = true
+charset = utf-8
+indent_style = space
+
+[*.html]
+indent_style = space
+indent_size = 2
+
+[*.{ts,json,js,tsx,jsx}]
+indent_style = space
+indent_size = 2
+
+[*.md]
+indent_size = 2
+indent_style = space
+
+[Dockerfile]
+indent_style = space
+indent_size = 2
+
+[*.{yml,yaml}]
+indent_size = 2
+indent_style = space

.eslintrc.cjs

@@ -19,6 +19,7 @@ var path = require('path');
 module.exports = {
   root: true,
   plugins: ['@spotify', 'notice', 'react', 'testing-library'],
+  ignorePatterns: ['.eslintrc.js', '.eslintrc.cjs'],
   rules: {
     'notice/notice': [
       'error',

.github/CODEOWNERS

@@ -8,27 +8,35 @@
 yarn.lock                                           @backstage/community-plugins-maintainers @backstage-service
 */yarn.lock                                         @backstage/community-plugins-maintainers @backstage-service
 
+/workspaces/3scale                                  @backstage/community-plugins-maintainers  @fmenesesg
+/workspaces/acr                                     @backstage/community-plugins-maintainers  @invincibleJai
 /workspaces/adr                                     @backstage/community-plugins-maintainers  @kuangp
+/workspaces/analytics                               @backstage/community-plugins-maintainers  @jmezach
 /workspaces/azure-devops                            @backstage/community-plugins-maintainers  @awanlin
 /workspaces/azure-storage-explorer                  @backstage/community-plugins-maintainers  @deepan10
-/workspaces/analytics                               @backstage/community-plugins-maintainers  @jmezach
 /workspaces/bitrise                                 @backstage/community-plugins-maintainers  @backstage/sda-se-reviewers
 /workspaces/blackduck                               @backstage/community-plugins-maintainers  @deepan10
 /workspaces/code-coverage                           @backstage/community-plugins-maintainers  @alde
 /workspaces/confluence                              @backstage/community-plugins-maintainers  @fjudith
 /workspaces/cost-insights                           @backstage/community-plugins-maintainers  @backstage/silver-lining
 /workspaces/entity-feedback                         @backstage/community-plugins-maintainers  @kuangp
 /workspaces/explore                                 @backstage/community-plugins-maintainers  @backstage/sda-se-reviewers
+/workspaces/feedback                                @backstage/community-plugins-maintainers  @riginoommen @deshmukhmayur @yashoswalyo
 /workspaces/fossa                                   @backstage/community-plugins-maintainers  @backstage/sda-se-reviewers
 /workspaces/git-release-manager                     @backstage/community-plugins-maintainers  @erikengervall
 /workspaces/github-pull-requests-board              @backstage/community-plugins-maintainers  @gregorytalita
+/workspaces/jfrog-artifactory                       @backstage/community-plugins-maintainers  @BethGriggs
 /workspaces/kafka                                   @backstage/community-plugins-maintainers  @andrewthauer
 /workspaces/linguist                                @backstage/community-plugins-maintainers  @awanlin
+/workspaces/nexus-repository-manager                @backstage/community-plugins-maintainers  @schultzp2020
 /workspaces/octopus-deploy                          @backstage/community-plugins-maintainers  @jmezach
+/workspaces/pingidentity                            @backstage/community-plugins-maintainers  @jessicajhee
 /workspaces/playlist                                @backstage/community-plugins-maintainers  @kuangp
+/workspaces/redhat-argocd                           @backstage/community-plugins-maintainers  @karthikjeeyar @rohitkrai03 @Eswaraiahsapram
+/workspaces/redhat-resource-optimization            @backstage/community-plugins-maintainers
+/workspaces/report-portal                           @backstage/community-plugins-maintainers  @yashoswalyo
 /workspaces/rollbar                                 @backstage/community-plugins-maintainers  @andrewthauer
+/workspaces/scaffolder-relation-processor           @backstage/community-plugins-maintainers  @04kash
 /workspaces/sonarqube                               @backstage/community-plugins-maintainers  @backstage/sda-se-reviewers
-/workspaces/user-settings                           @backstage/community-plugins-maintainers  @backstage/sda-se-reviewers
 /workspaces/tech-insights                           @backstage/community-plugins-maintainers  @xantier
-/workspaces/report-portal                           @backstage/community-plugins-maintainers  @yashoswalyo
-/workspaces/redhat-resource-optimization            @backstage/community-plugins-maintainers
+/workspaces/user-settings                           @backstage/community-plugins-maintainers  @backstage/sda-se-reviewers

.github/PULL_REQUEST_TEMPLATE.md

@@ -7,8 +7,8 @@
 
 <!--- Please include the following in your Pull Request when applicable: -->
 
-- [ ] A changeset describing the change and affected packages. ([more info](https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md#creating-changesets))
+- [ ] A changeset describing the change and affected packages. ([more info](https://github.com/backstage/community-plugins/blob/master/CONTRIBUTING.md#creating-changesets))
 - [ ] Added or updated documentation
 - [ ] Tests for new functionality and regression tests for bug fixes
 - [ ] Screenshots attached (for UI changes)
-- [ ] All your commits have a `Signed-off-by` line in the message. ([more info](https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md#developer-certificate-of-origin))
+- [ ] All your commits have a `Signed-off-by` line in the message. ([more info](https://github.com/backstage/community-plugins/blob/master/CONTRIBUTING.md#developer-certificate-of-origin))

.github/renovate.json

@@ -27,6 +27,10 @@
       "matchPackageNames": ["node-fetch"],
       "allowedVersions": "<3.0.0"
     },
+    {
+      "matchPackageNames": ["typescript"],
+      "allowedVersions": "~5.3.0"
+    },
     {
       "matchPackageNames": ["yn"],
       "allowedVersions": "<5.0.0"

.github/workflows/automate-staleness.yml

@@ -0,0 +1,39 @@
+name: Automate staleness
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: '0 */6 * * *'  # Runs every 6 hours
+permissions:
+  contents: read
+jobs:
+  stale:
+    permissions:
+      issues: write
+      pull-requests: write
+    runs-on: ubuntu-latest
+    steps:
+      - name: Harden Runner
+        uses: step-security/harden-runner@5c7944e73c4c2a096b17a9cb74d65b6c2bbafbde # v2.9.1
+        with:
+          egress-policy: audit
+
+      - uses: actions/stale@v9
+        id: stale
+        with:
+          stale-issue-message: >
+            This issue has been automatically marked as stale because it has not had
+            recent activity. It will be closed if no further activity occurs. Thank you
+            for your contributions.
+          days-before-issue-stale: 60
+          days-before-issue-close: 7
+          stale-issue-label: stale
+          stale-pr-message: >
+            This PR has been automatically marked as stale because it has not had
+            recent activity from the author. It will be closed if no further activity occurs.
+            If the PR was closed and you want it re-opened, let us know
+            and we'll re-open the PR so that you can continue the contribution!
+          days-before-pr-stale: 14
+          days-before-pr-close: 7
+          stale-pr-label: stale
+          operations-per-run: 100
+

.github/workflows/automate_renovate_changesets.yml

@@ -28,6 +28,6 @@ jobs:
           git config --global user.name 'Github changeset workflow'
 
       - name: Generate feedback
-        uses: backstage/actions/[email protected].10
+        uses: backstage/actions/[email protected].13
         with:
           multiple-workspaces: true

.github/workflows/ci.yml

@@ -14,16 +14,18 @@ jobs:
     outputs:
       workspaces: ${{ steps.find-changed-workspaces.outputs.workspaces }}
     steps:
-      - name: Checkout base branch for diff purposes
-        uses: actions/checkout@1d96c772d19495a3b5c517cd2bc0cb401ea0529f # v4
-        with:
-          ref: ${{ github.event.pull_request.base.ref }}
-
       - name: Calculate number of commits in PR
         id: calculate-commits
         env:
           COMMITS: ${{ github.event.pull_request.commits }}
         run: echo "NUMBER_OF_COMMITS=$(($COMMITS + 1))" >> $GITHUB_ENV
+
+      - name: Checkout base branch for diff purposes
+        uses: actions/checkout@1d96c772d19495a3b5c517cd2bc0cb401ea0529f # v4
+        with:
+          ref: ${{ github.event.pull_request.base.ref }}
+          fetch-depth: 50 # TODO(awanlin): Temporary fix
+
       - name: Checkout head branch
         uses: actions/checkout@1d96c772d19495a3b5c517cd2bc0cb401ea0529f # v4
         with:

.github/workflows/release_workspace.yml

@@ -76,6 +76,10 @@ jobs:
       - name: Fetch previous commit for release check
         run: git fetch origin '${{ github.event.before }}'
 
+      - name: Fetch the commit that triggered the workflow (used by backstage/changesets-action)
+        run: git fetch origin ${{ github.sha }}
+        continue-on-error: true
+
       - name: Check if release
         id: release_check
         if: inputs.force_release != true

.github/workflows/renovate.yml

@@ -30,15 +30,15 @@ jobs:
     name: Renovate
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
 
       # This third party action allows you to download the cache artifact from different workflow runs
       # Note that actions/cache doesn't work well because the cache key would need to be computed from
       # a file within the cache, meaning there would never be any data to restore. With other keys, the
       # cache wouldn't necessarily upload when it changes. actions/download-artifact also doesn't work
       # because it only handles artifacts uploaded in the same run, and we want to restore from the
       # previous successful run.
-      - uses: dawidd6/action-download-artifact@v2
+      - uses: dawidd6/action-download-artifact@v5
         if: github.event.inputs.repoCache != 'disabled'
         continue-on-error: true
         with:
@@ -97,7 +97,7 @@ jobs:
           # To solve *that*, we'd have to extract to root (/), which isn't safe.
           tar -czvf $cache_archive -C $cache_dir .
 
-      - uses: actions/upload-artifact@v3
+      - uses: actions/upload-artifact@v4
         if: github.event.inputs.repoCache != 'disabled'
         with:
           name: ${{ env.cache_key }}

.github/workflows/version-bump.yml

@@ -68,7 +68,7 @@ jobs:
 
       - name: 'Set release name'
         id: set_release_name
-        run: node scripts/ci/set-release-name.js ${{ matrix.workspace }}
+        run: node scripts/ci/set-release-name.js ${{ matrix.workspace }} ${{ inputs.release_line || 'main' }}
       - name: 'Configure git'
         run: |
           git config --global user.email "41898282+github-actions[bot]@users.noreply.github.com"

CONTRIBUTING.md

@@ -22,6 +22,7 @@ If you have questions or feedback regarding Community Plugins, you can visit the
   - [Creating new plugins or packages in a Workspace](#creating-new-plugins-or-packages-in-a-workspace)
   - [Migrating a plugin](#migrating-a-plugin)
     - [Manual migration steps](#manual-migration-steps)
+  - [Organization Membership Request for CODEOWNERS](#organization-membership-request-for-codeowners)
   - [Developer Certificate of Origin](#developer-certificate-of-origin)
   - [API Reports](#api-reports)
   - [Submitting a Pull Request](#submitting-a-pull-request)
@@ -160,6 +161,8 @@ By migrating a plugin to this repository you will need to ensure you can meet ce
 - Agree to publish the plugin to the `@backstage-community` npm scope.
 - Adopt the Changesets workflow for releasing new plugin versions.
 - Adhere to the repository security process for handling security-related issues.
+- Agree to commit to the responsibilities and requirements listed in the [Plugin Maintainer's role
+](https://github.com/backstage/community/blob/main/GOVERNANCE.md#plugin-maintainer).
 - Plugins moved to the repository should be licensed under Apache 2.0.
 
 ### Manual migration steps
@@ -191,11 +194,46 @@ cp -r ../existing-plugins/plugins/plugin-name plugins/
 
 6. Add maintainers to the `CODEOWNERS` file for the new workspace.
 
+> **Note:** The `CODEOWNERS` file will have errors until the [Organization Membership Request for CODEOWNERS](#organization-membership-request-for-codeowners) has been approved. However, it is still useful to add `CODEOWNERS` as this point as it provides a documented reference as to who owns/maintains the plugin.
+
 7. Create a new pull request from your branch.
 
 8. Update external references to the old plugin location such as documentation to point to the new location in the `backstage/community-plugins` repository.
 
-9. In the original repository, update the plugin to indicate that it has been moved to the `backstage/community-plugins` repository. You may wish to deprecate the old version on npm.
+9.  In the original repository, update the plugin to indicate that it has been moved to the `backstage/community-plugins` repository. You may wish to deprecate the old version on npm.
+
+## Organization Membership Request for CODEOWNERS
+
+This section outlines the process for plugin maintainers to request organization membership in the Backstage community, which is necessary for efficiently managing `CODEOWNERS` in this repository.
+
+Plugin maintainers can request organization membership by submitting a request through [this link](https://github.com/backstage/community/issues/new/choose) and filling out the provided form. In the request, they should:
+
+- List the plugins they have contributed and/or maintain within the 'Highlighted Contributions' section.
+- Ping the [Community Plugins Area Maintainers](https://github.com/backstage/community/tree/main/project-areas/community-plugins#community-plugin-area-maintainers) for review and support of the request.
+
+As becoming an organization member provides elevated permissions, addition of new organization members follows a vetting process, while hoping not to create unnecessary barriers for new plugin maintainers. The following criteria are often used for the vetting process:
+
+- Is the individual a member of other teams in Backstage?
+- What is the length and consistency of their involvement with Backstage plugins and/or the Backstage community?
+- Are there other contributors or plugin maintainers who work with the individual and can vouch for them?
+- Do they have an employer with a vested interest in the Backstage community?
+
+The Community Plugins Area Maintainers will review the request. While the request is being processed, plugin maintainers are encouraged to review and approve PRs related to their plugins, even though it will not yet show up as a formal review in the GitHub UI.
+
+**Form Details:**
+
+- **Name**: Organization Membership Request
+- **Description**: A request to become a Backstage organization member
+- **Title**: Org Member: `<your-github-login>`
+- **Labels**: `org-member-request`
+
+The form includes fields to confirm adherence to the Code of Conduct, list highlighted contributions, and more. Please ensure you provide:
+
+1. The plugins you maintain within the community plugins section.
+2. Links to your notable contributions (PRs, issues, etc.).
+3. A list of other plugin maintainers who can vouch for your request.
+
+Once the form is submitted, the plugin maintainers will review your request and provide feedback or support as needed.
 
 ## Developer Certificate of Origin