Asher 2d08e6e95b

Refactor releases to use VS Code packaging ...

Instead of building the linux-x64 package, stripping the modules, then
installing them again, we build the correct target and use the modules
as they are.

This means we do not have to copy all the post-processing steps like the
ones that delete unnecessary modules.

For the NPM package we still publish the linux-x64 package (without
modules of course).  This means npm installations do not get that same
post-processing.

Another advantage of this is that we can run the release immediately
without having to wait for the build step, or on a commit that no longer
has a build artifact, since they all build individually now.  We could
try sharing the core-ci build step, but leaving that alone for now.

I also converted the macOS jobs into a matrix.

Deleted the CI readme because it was out of date and seemed to just
repeat what should be described in the scripts anyway.

Removed a section about Homebrew since we do not maintain that anymore.

It looks like there is no need to symlink node_modules.asar anymore.

2026-03-27 16:15:44 -08:00

..

docker-buildx-push.sh

refactor: get version dynamically (#5753)

2022-11-08 22:45:01 +00:00

steps-lib.sh

feat(brew-bump): add check for cleanup step

2021-09-28 16:07:01 -07:00