fix(deps): update dependency alasql to v4.19.0 - #2516
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
force-pushed
the
renovate/alasql
branch
3 times, most recently
from
September 7, 2026 13:00
15c76bb to
077ab98
Compare
1 task
dawsontoth
approved these changes
Sep 7, 2026
dawsontoth
left a comment
Contributor
There was a problem hiding this comment.
Verified locally and safe to merge. macOS, Node 24.19.0, npm 11.17.0, worktree at 077ab980f.
npm ci→ exit 0 (lockfile is in sync;react-native*pruning is not present on this branch)npm run build→ exit 0, notscdiagnostics- SQL suites —
sqlTranslator/**,sqlEngine/**,dataLayer/sql-update,dataLayer/SQLSearch,utility/functions/sql/alaSQLExtension: 258 passing / 8 pending / 0 failing, identical to the base commit38fcbf1. Those are the suites that actually exercise alasql (sqlEngine/parser/*,sqlTranslator/*,dataLayer/SQLSearch.tsall import it).
Diff is a single line: alasql 4.18.0 → 4.19.0 in package.json, plus the matching lockfile entry. No transitive movement.
The red Unit Test checks are a main defect, not this PR
Unit Test (Node.js v22/v24/v26) all fail on exactly one test:
1) test MQTT connections and commands
subscribe to retained record with patch operations:
Uncaught AssertionError [ERR_ASSERTION]: 'update 3' == 'update 2'
at unitTests/apiTests/mqtt-test.mjs:503:14
Deterministic, 3/3 Node versions. It cannot plausibly be alasql — it's MQTT retained-record patch ordering. Two independent controls confirm it's on main:
- #2515 (a completely different dependency set) fails on the identical assertion, all three Node versions.
- #2476, an unrelated feature PR run against the same base this morning at 13:07, fails on the identical assertion too.
Filing that separately. Approving here on the strength of the build + SQL parity; the MQTT check will go green once main is fixed.
renovate
Bot
force-pushed
the
renovate/alasql
branch
from
September 8, 2026 12:34
077ab98 to
cd3e9da
Compare
renovate
Bot
force-pushed
the
renovate/alasql
branch
from
September 8, 2026 15:45
cd3e9da to
38a9e78
Compare
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 PR contains the following updates:
4.18.0→4.19.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
alasql/alasql (alasql)
v4.19.0: 2026-08-25Compare Source
What's Changed
New Contributors
Full Changelog: AlaSQL/alasql@v4.18.0...v4.19.0
Configuration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.