[release] Merge Develop into Master

.github/workflows/ci.yml

@@ -21,12 +21,6 @@ jobs:
       - name: Run unit tests
         run: >-
           npm run test:unit -- --coverage
-      - name: Upload coverage reports to Codecov
-        uses: codecov/codecov-action@v4.5.0
-        with:
-          os: linux
-          token: ${{ secrets.CODECOV_TOKEN }}
-          fail_ci_if_error: true # build should fail if Codecov runs into an error during upload
   cypress:
     name: Run Cypress tests
     runs-on: ubuntu-latest

.github/workflows/create_release_pr.yml

@@ -0,0 +1,12 @@
+# Create or update merge-to-master pull requests for production releases
+# Note that by design, creating or editing a PR will not trigger a downstream `pull_request` event as this could lead to recursion
+name: Release
+
+on:
+  push:
+    branches:
+      - develop
+
+jobs:
+  pull_request:
+    uses: sanger/.github/.github/workflows/create-release-pr.yml@master

.nvmrc

@@ -1 +1 @@
-v23.10.0
+v24.14.0

.prettierignore

@@ -1,6 +1,7 @@
 .DS_Store
 node_modules
 dist
+CONTRIBUTING.md
 
 tests/e2e/reports/
 selenium-debug.log

CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# Contributing
+
+All contributions to this project are subject to the [MIT License](https://foss-haas.mit-license.org/). By submitting a contribution, you agree to license your work under these terms.
+
+## Contribution Process
+
+### 1. Issue First
+
+All contributions from outside the core team require an **Issue First** approach. Before submitting a pull request (PR), you must:
+
+- Open an issue in the repository.
+- Ensure the issue includes:
+  - **Clear problem statement:** Describe the issue or feature request.
+  - **Reproduction steps:** If reporting a bug, provide steps to reproduce it.
+  - **Proposed approach:** Outline your suggested solution or implementation.
+  - **Why this change matters:** Explain the impact or necessity of the change.
+- Tag `@sanger/psd-developers` in the issue to bring it to the attention of a maintainer.
+- Wait for the issue to be assigned or approved by a maintainer.
+
+### 2. Pull Request
+
+Once your issue is approved:
+
+- Fork the repository and create a branch for your changes.
+- Submit a PR referencing the approved issue.
+- Ensure your code adheres to the project's coding standards and passes all tests.
+
+### 3. Review
+
+Maintainers will review your PR. Address any feedback before merging.

eslint.config.js

@@ -32,6 +32,7 @@ export default [
       globals: {
         ...globals.node,
         ...globals.jest,
+        ...globals.browser,
         // Global vitest and Cypress variables so they don't violate no-undef
         vi: 'readonly',
         cy: 'readonly',