Generalise npm publishing workflow to work for more than just shared-components (#33086)

* Generalise npm publishing workflow to work for more than just shared-components

* Update doc

Author: t3chguy

…/workflows/shared-component-publish.yaml .github/workflows/npm-publish.yaml.github/workflows/shared-component-publish.yaml renamed to .github/workflows/npm-publish.yaml .github/workflows/shared-component-publish.yaml renamed to .github/workflows/npm-publish.yaml

@@ -1,6 +1,15 @@
-name: Publish shared component npm package
+name: Publish npm package
+run-name: Publish ${{ inputs.package }}
 on:
-    workflow_dispatch: {}
+    workflow_dispatch:
+        inputs:
+            package:
+                description: Which package to release
+                required: true
+                type: choice
+                options:
+                    - playwright-common
+                    - shared-components
 
 concurrency: release
 jobs:
@@ -29,10 +38,9 @@ jobs:
             - name: Update npm
               run: npm install -g npm@latest
 
-            # Need to setup element web too as it needs the translations
-            - name: 🛠️ Setup EW
+            - name: 🛠️ Install dependencies
               run: pnpm install --frozen-lockfile
 
             - name: 🚀 Publish to npm
-              working-directory: packages/shared-components
+              working-directory: packages/${{ inputs.package }}
               run: npm publish --access public --provenance

packages/shared-components/README.md

@@ -365,4 +365,4 @@ pnpm i18n
 Two steps are required to publish a new version of this package:
 
 1. Bump the version in `package.json` following semver rules and open a PR.
-2. Once merged run the [github workflow](https://github.com/element-hq/element-web/actions/workflows/shared-component-publish.yaml)
+2. Once merged run the [github workflow](https://github.com/element-hq/element-web/actions/workflows/npm-publish.yaml)