Repository navigation
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



This pull request updates the project to support Node.js 26 across the development environment, CI workflows, and documentation, along with minor dependency and bug fixes. The most important changes are grouped below:
Node.js Version Upgrades:
.devcontainer/Dockerfileto usenode:26-alpineinstead ofnode:24-alpine, ensuring local development uses Node.js 26.master.yml,sonar.yml,staging.yml) to use Node.js 26 for builds and tests, including adding Node.js 26 to the test matrix and as the default version. [1] [2] [3] [4]Dependency Updates:
@typescript-eslint/eslint-pluginand@typescript-eslint/parserto version^8.72.1inpackage.jsonfor improved linting compatibility.v8.4.0in workflows for improved scanning and compatibility. [1] [2]Bug Fixes:
src/lib/bypasser/index.jswhereBypasser.forget()could incorrectly attempt to remove a non-existent key by checking if the index is valid before splicing.Testing Improvements:
tests/switcher-stub.test.jsto verify that multiple keys can be assumed and stacked correctly in the client.