Skip to content

Modernize repository - #212

Merged
rubensworks merged 1 commit into
masterfrom
modernize-repository
Aug 19, 2026
Merged

Modernize repository#212
rubensworks merged 1 commit into
masterfrom
modernize-repository

Conversation

@jitsedesmet

@jitsedesmet jitsedesmet commented Jul 30, 2026

Copy link
Copy Markdown

Feature branch that will be rebased onto master when modernization is done.
Aims to close #206

This work is ongoing by @Michiel-VandeVelde

This starts the CI, dependency, and build modernization, targeting the shared modernize-repository branch @jitsedesmet set up upstream.

Covers: GitHub Actions bumped to non-deprecated versions targeting Node.js 24, Docker base image updated to node:22-slim, HDT's native build fixed for modern Node, sinon/sinon-chai modernization attempted then reverted (pinned sinon-chai to 2.14.0 instead the newer sinon API broke stub.reset() usage elsewhere), and lerna pinned to a version that keeps HDT's native build working at the root.
@jitsedesmet jitsedesmet mentioned this pull request Jul 30, 2026
@jitsedesmet jitsedesmet changed the title Modernize CI Modernize repository Aug 19, 2026

@rubensworks rubensworks left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one minor question, looks good otherwise!

Comment thread package.json
"eslint": "^7.0.0",
"eslint-plugin-import": "^2.22.0",
"lerna": "^4.0.0",
"lerna": "9.0.7",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason why this is pinned? (not using ^)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lerna was bumped 4 -> 9.0.7 to fix hdt's native build, i fixed the issue on the Typescript branch, kept lerna at ^4.0.0 and solved the same hdt/node-gyp problem with an explicit node-gyp: ^11.0.0 devDependency instead. So we can revert this change

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean reverting it here in this branch (before the PR is merged)?
Or will be be reverted later on in the other PR?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will be be reverted later on in the other PR

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok! Then this PR should be good to go. @jitsedesmet do you agree if I merge this one?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, We can merge this (but not squash). Then we can just target main directly from now on?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done! Ok to target master from now on.

@rubensworks
rubensworks marked this pull request as ready for review August 19, 2026 09:54
@rubensworks
rubensworks merged commit 6d02902 into master Aug 19, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Modernize repository

3 participants