The build scripts run on GNU/Linux and macOS. The Windows binaries are generated on x64 GNU/Linux, using mingw-w64.
For details on installing the prerequisites, please read the Build Prerequisites page.
The project is hosted on GitHub:
To clone the stable branch (xpack), run the following commands in a
terminal (on Windows use the Git Bash console):
rm -rf ~/Work/xpack-dev-tools/xbb-helper-xpack.git && \
mkdir -p ~/Work/xpack-dev-tools && \
git clone \
https://github.com/xpack-dev-tools/xbb-helper-xpack.git \
~/Work/xpack-dev-tools/xbb-helper-xpack.gitFor development purposes, clone the xpack-development branch:
rm -rf ~/Work/xpack-dev-tools/xbb-helper-xpack.git && \
mkdir -p ~/Work/xpack-dev-tools && \
git clone \
--branch xpack-development \
https://github.com/xpack-dev-tools/xbb-helper-xpack.git \
~/Work/xpack-dev-tools/xbb-helper-xpack.gitLink it to the user global xPacks store:
xpm link -C ~/Work/xpack-dev-tools/xbb-helper-xpack.gitFurther updates can be done with:
git -C ~/Work/xpack-dev-tools/xbb-helper-xpack.git pullThere are no scheduled releases, the project is updated when necessary.
Before starting the build, perform some checks and tweaks.
In the xpack-dev-tools/xbb-helper-xpack Git repo:
- switch to the
xpack-developmentbranch - pull new changes
- if needed, merge the
xpackbranch
No need to add a tag here, it'll be added when the release is created.
Determine the next version (like 5.4.2) and update the
package.json file; the format is 5.4.2-pre.
Check GitHub issues and pull requests:
and fix them; assign them to a milestone (like 5.4.2).
Normally README.md should not need changes, but better check.
Information related to the new version should not be included here,
but in the version specific release page.
- update version in
README-MAINTAINER.md - update version in
README.md
Use the new version, suffixed by pre, like 5.4.2-pre.
- open the
CHANGELOG.mdfile - check if all previous fixed issues are in
- add a new entry like * v5.4.2 released
- commit with a message like prepare v5.4.2
- commit and push
- none
- select the
xpack-developmentbranch - commit all changes
npm packand check the content of the archive; possibly adjust.npmignorenpm version 5.4.2- push the
xpack-developmentbranch to GitHub - the
postversionnpm script should also update tags viagit push origin --tags
- merge
xpack-developmentintoxpack - push to GitHub
Update the version in templates/common/_xpack-dev-tools/build-assets/package-merge-liquid.json.
"@xpack-dev-tools/xbb-helper": "github:xpack-dev-tools/xbb-helper-xpack#v5.4.2"Open the workspace with all packages, and update all references with
"@xpack-dev-tools/xbb-helper": "github:xpack-dev-tools/xbb-helper-xpack#v5.4.2"Support is provided by the xpacks/npm-packages-helper.git project.
To run for all projects, remove the stamps in the /xpack-dev-tools.github/stamps/projects-generate-commons-and-build folder.
Run the following xpm actions:
xpack-dev-tools-generate-top-commonsxpack-dev-tools-commit-and-push-top-commons
Support is provided by the xpacks/docusaurus-template-liquid.git project.
To run for all projects, remove the stamps in the /xpack-dev-tools.github/stamps/websites-generate-commons-and-build folder.
Run the following xpm actions:
xpack-dev-tools-generate-websites-commons-and-buildxpack-dev-tools-commit-and-push-websites