Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions .github/workflows/build-test.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
name: CI

on:
workflow_dispatch:
push:
branches: [ main ]
pull_request:
branches: [ main ]

permissions:
contents: read

jobs:
test:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
node: [20, 22, 24, 25]
steps:
- uses: actions/checkout@v6
- uses: actions/setup-node@v6
id: node
with:
node-version: ${{ matrix.node }}
cache: npm
- name: "Install, lint and build production outputs (Node ${{ steps.node.outputs.node-version }})"
run: |
npm run build-package
- name: "Build development outputs and (Xvfb) run JS tests in Firefox & Chrome"
run: |
firefox --version
google-chrome --version
xvfb-run npm test
22 changes: 0 additions & 22 deletions .github/workflows/node.js.yml
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmh git eventually decided there's too many changes along with the rename to track it as deletion and new addition instead of diffing the file:/ (I've renamed it from its GHA boilerplate defaults to actually match other uses to describe its content)… I see how this is not ideal, but I've made a diff on the side to hopefully make the changes more reviewable:

diff

This file was deleted.

5 changes: 5 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -148,6 +148,11 @@ should also be updated so the documentation site matches the NPM package feature
2. Make sure your local `main` branch is up to date.
3. Push the `main` branch to the `prod` branch: `git push origin main:prod`.

_(The same is triggered by submitting a new GitHub Release, so the steps above can be
skipped if you plan to publish a GitHub Release for the version tag — which you should.
In such case the site deployment will be taken care of by automation, publishing the
reference the release tag actually points to.)_

A notice will be posted in #www-notify on Slack when the push has completed.

### Pushing to demo
Expand Down