Commit graph

14 commits

Author SHA1 Message Date
Marc Durdin
f29133d0ba maint(resources): set build flags for npm-publish
Test-bot: skip
Build-bot: skip
2025-10-29 12:09:38 +01:00
Marc Durdin
785a745f9b maint(resources): don't report status check on release builds for npm-publish
This matches the pattern from deb-packaging.yml. It would be worth
reviewing why the sha doesn't match up?

Build-bot: skip
Test-bot: skip
2025-10-29 11:38:20 +01:00
Marc Durdin
f9b25890b6 maint(resources): add meson and emscripten setup to npm-publish
Also splits the build and publish steps so all packages are built before
first is published, as publishing stomps on package.json files, which
makes subsequent builds trickier.

This needs to be merged to master in order for the action steps to pass.

Build-bot: skip
Test-bot: skip
2025-10-29 10:27:29 +01:00
Marc Durdin
3040c72174 maint(resources): skip nvm in npm-publish script
Test-bot: skip
Build-bot: skip
2025-10-28 15:28:24 +01:00
Marc Durdin
a4779a7f93 maint(resources): add write permission for statuses for npm-publish
Build-bot: skip
Test-bot: skip
2025-10-28 15:04:19 +01:00
Marc Durdin
b582e3c0fb maint(resources): improve reporting of status for npm-publish
Build-bot: skip
2025-10-28 14:14:42 +01:00
Marc Durdin
f1368dd418 maint(resources): rename npm-publish workflow and give detailed title 2025-10-28 13:34:37 +01:00
Marc Durdin
49161075f3 maint(resources): lower case npm 2025-10-28 13:30:57 +01:00
Marc Durdin
0f6b4d52e0 maint(resources): add commit status check for npm-publish
Build-bot: skip release:developer
2025-10-28 13:29:40 +01:00
Marc Durdin
844219f2cb maint(resources): set env variables in npm publish GHA
Test-bot: skip
Build-bot: skip
2025-10-28 11:14:22 +01:00
Marc Durdin
794faedbde maint(resources): remove gh status check for npm-publish
Build-bot: skip
2025-10-28 09:00:40 +01:00
Marc Durdin
fe484826ac maint(resources): use a string for version, rather than number
Test-bot: skip
Build-bot: skip
2025-10-28 08:59:27 +01:00
Marc Durdin
971d67e266 maint(resources): use actions/setup-node to upgrade npm
We don't have permissions to use `npm install --global npm` to get a
specific version, but this action is supported by GH so should be fine.

It remains to be seen if there will be other compatibility issues due to
being a later version of Node than what we are using in v19.

Build-bot: skip
Test-bot: skip
2025-10-28 08:12:15 +01:00
Marc Durdin
ba411774f6 maint(resources): move NPM package publishing to GitHub Actions
Due to recent changes in NPM package publishing security requirements,
we have to move from TeamCity build to a GitHub Action to publish our
NPM packages, so we can take advantage of trusted publishing. This
change also consolidates and centralizes the npm publishing into
resources/build/ci/npm-publish.sh, which removes a lot of boilerplate
from each of the build.sh scripts, and ensures consistency.

Packages will be `npm pack`ed on PR and test builds, and published in
release builds.

Ref: https://docs.npmjs.com/trusted-publishers
Ref: https://github.blog/changelog/2025-09-29-strengthening-npm-security-important-changes-to-authentication-and-token-management/
Fixes: #14963
Test-bot: skip
Build-bot: release:developer
2025-10-27 16:31:55 +01:00