Seems like we need to update the CI image using [1]. Dominik
[1] https://ci-builds.apache.org/job/KIE/job/kie-tools/job/main/job/ci/job/kie-tools-ci-image-build/job/main/ On Mon, 23 Feb 2026 at 10:13, Dominik Hanak <[email protected]> wrote: > Hello everyone, > > does anyone know what steps to take to make pnpm and node of these > versions to be available on > the apache jenkins for our jobs[1]? Will probably become a problem when we > will run the release. > > You can see the failure here [2]. > > Dominik > > [1] https://ci-builds.apache.org/job/KIE/job/kie-tools/ > [2] > https://ci-builds.apache.org/job/KIE/job/kie-tools/job/main/job/kie-tools-daily-dev-publish/888/cloudbees-pipeline-explorer/?filter=101 > > On Wed, 11 Feb 2026 at 02:12, Tiago Bento <[email protected]> wrote: > >> I see this was merged today. Thank you Thiago for the notice in >> advance and the clear instructions for local development. >> >> I use a Debox setup, and I had to run `diskutil apfs deleteVolume "Nix >> Store"` on macOS Tahoe after fetching the latest commit, as the error >> message instructed me to. >> >> After that I was able to run a `pnpm bootstrap` normally. >> >> >> On Mon, Feb 9, 2026 at 7:59 AM Thiago Lugli <[email protected]> wrote: >> > >> > I'll merge this PR tomorrow, as the longer it takes, the harder it is >> > to keep it updated. >> > If you haven't already, please check it out and see how it could >> > affect your work. >> > >> > Here are the instructions for updating your local clone once the PR is >> merged: >> > >> > The easiest way to make sure your environment is clean is to: >> > >> > - MAKE SURE ALL YOUR CHANGES ARE COMMITTED >> > - Run `pnpm cache delete`; >> > - Clone the repository again (or run `git clean -fdx`); >> > - Update your local build tools (Node.js and pnpm) or start the devbox >> > shell with the new versions; >> > - Run `pnpm bootstrap`. >> > >> > If you don't want to clone or clean your local repository, at least: >> > >> > - Delete the root node_modules; >> > - Run `pnpm cache delete`; >> > - Update your local build tools (Node.js and pnpm) or start the devbox >> > shell with the new versions; >> > - Run `pnpm bootstrap`. >> > >> > Installing all dependencies again might take a while, so reserve some >> > downtime for doing this upgrade. >> > >> > Thanks! >> > >> > On Sun, Feb 1, 2026 at 3:32 PM Thiago Lugli <[email protected]> >> wrote: >> > > >> > > Hello, >> > > >> > > As part of our efforts to keep the apache/incubator-kie-tools >> > > repository up to date and free of vulnerabilities, I've raised a PR >> > > [1] to upgrade the Node.js version from 22.14.0 to 24.13.0 and pnpm >> > > from 9.3.0 to 10.28.2. >> > > >> > > These upgrades introduce breaking changes ([2] and [3]) that were >> > > fixed in the PR but will require developer attention going forward. >> > > For example, adding dependencies with install/postinstall scripts now >> > > requires the developer to manually add them to the >> > > `pnpm.onlyBuiltDependencies` property in the root package.json file in >> > > order to allow the execution of these scripts. >> > > >> > > After the PR is merged, it is recommended that >> > > apache/incubator-kie-tools developers clean their local repository, >> > > install the new Node.js and pnpm versions, then run `pnpm bootstrap` >> > > again (see the PR's description for more information). >> > > >> > > The PR checks are green, meaning all our tests are passing, but I >> > > would still like some help double-checking our packages for any >> > > untested code that could be affected by this change. >> > > >> > > It's also worth noting that our release pipelines will need to reflect >> > > the new Node.js and pnpm versions. I haven't looked at them yet, but I >> > > would appreciate some help figuring out what and where needs to be >> > > updated. >> > > >> > > [1] https://github.com/apache/incubator-kie-tools/pull/3414 >> > > [2] https://nodejs.org/en/blog/migrations/v22-to-v24 >> > > [3] https://github.com/pnpm/pnpm/releases/tag/v10.0.0 >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
