Ci/modernise actions - #12

Merged

ariesclark merged 20 commits into

mainfrom

ci/modernise-actions

Aug 9, 2026

Commits on Aug 9, 2026

ci: bump actions and node to 24 so the generator loads
ariesclark
committed
a171b84
ci: run build and test workflows on every branch
ariesclark
committed
8355ebe
ci: use the shared SDK specification action
ariesclark
committed
2446494
ci: generate from the legacy bundle this SDK ships from
ariesclark
committed
47f7dff
ci: build against the bundle this SDK generates from
ariesclark
committed
e057ed7
ci: let setup decide where the bundle comes from
ariesclark
committed
3b7b0d5
ci: cache dependencies and drop redundant setup
ariesclark
committed
999942e
ci: run the generator from its jar instead of an npm wrapper
ariesclark
committed
9f55dda
ci: use the renamed setup-generator and download actions
ariesclark
committed
0d79269
ci: split the checks into their own jobs and separate release
ariesclark
committed
1c749e1
ci: give generation its own job ahead of the checks
ariesclark
committed
d3ce494
ci: fold the standalone checks into the ci workflow
ariesclark
committed
fd03a7e
ci: run the checks once per change
ariesclark
committed
a028543
ci: run the checks on every branch
ariesclark
committed
6be7cb5
ci: report how to install what this run built
ariesclark
committed
73dafac
ci: report how to install what this run built
ariesclark
committed
8e64040
ci: let each SDK report itself
ariesclark
committed
6f2b408
ci: publish from the ci workflow
ariesclark
committed
a14c7ff
fix(ci): only publish from the SDK's own repository
ariesclark
committed
1caadb9
ci: use the actions from the specification's main branch
ariesclark
committed
a34258f

Navigation Menu

Uh oh!

Ci/modernise actions - #12

Ci/modernise actions#12
ariesclark merged 20 commits into
mainfrom
ci/modernise-actions

Commits on Aug 9, 2026

ci: bump actions and node to 24 so the generator loads

ci: run build and test workflows on every branch

ci: use the shared SDK specification action

ci: generate from the legacy bundle this SDK ships from

ci: build against the bundle this SDK generates from

ci: let setup decide where the bundle comes from

ci: cache dependencies and drop redundant setup

ci: run the generator from its jar instead of an npm wrapper

ci: use the renamed setup-generator and download actions

ci: split the checks into their own jobs and separate release

ci: give generation its own job ahead of the checks

ci: fold the standalone checks into the ci workflow

ci: run the checks once per change

ci: run the checks on every branch

ci: report how to install what this run built

ci: report how to install what this run built

ci: let each SDK report itself

ci: publish from the ci workflow

fix(ci): only publish from the SDK's own repository

ci: use the actions from the specification's main branch