[cs-raj]

Summary

Sets the package version on development to 2.1.12 and refreshes package-lock.json, so the next release is a single patch on top of the last published version.

Why

	Version
npm latest	2.1.11
master	2.1.14 (never published)
development (before this PR)	2.1.14

2.1.12 never reached npm: the v2.1.12 release run failed at the "Publish to npm" step. 2.1.13 and 2.1.14 were bumped by Snyk-fix PRs and never released. Setting development to 2.1.12 keeps the next release at 2.1.11 → 2.1.12.

Changes

• package.json, package-lock.json: version 2.1.14 → 2.1.12
• package-lock.json: updates within the existing version ranges, for @babel/generator, @babel/helper-string-parser, @babel/parser, @babel/traverse, @babel/types, baseline-browser-mapping, browserslist, caniuse-lite, electron-to-chromium, node-releases and ts-jest (29.4.15). package.json changes only the version, and there are no source changes.

Verification

Run on this branch in a clean copy, Node 24 / npm 11:

• npm ci and npm run build-ts (tsc) pass
• npm audit: unchanged by this PR, 23 findings before and after (4 low, 19 moderate, 0 high)
• Tests: 13 failed / 10 passed of 23, identical on current development without this change, so it is not caused by this PR (failures are TypeError: Cannot read properties of undefined (reading 'branch')). Jest also needs --notify=false here, because jest.config sets notify: true and node-notifier isn't installed.

Known issue: check-version-bump will fail

The check fails when package.json's version equals the latest reachable tag. The latest tag is v2.1.12, which belongs to the failed release above, so 2.1.12 equals it. Before this can merge, either:

• delete the stale v2.1.12 GitHub release and tag, since nothing was published from it, or
• use 2.1.13 instead.

I have not deleted or changed the tag or release.

🤖 Generated with Claude Code

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	1	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 0
• Medium without fixes: 1
• Low without fixes: 0

✅ BUILD PASSED - All security checks passed