chore(deps): bump stack-trace from 0.0.10 to 1.0.0

[dependabot]

Bumps stack-trace from 0.0.10 to 1.0.0.

Release notes

Sourced from stack-trace's releases.

v1.0.0

What's Changed

• Updated CallSite object API link by @​DylanTackoor in felixge/node-stack-trace#28
• test on Node.js 8 by @​mightyiam in felixge/node-stack-trace#24
• fix test-long-stack-trace.js by @​mightyiam in felixge/node-stack-trace#23
• use npm scripts instead of Makefile by @​mightyiam in felixge/node-stack-trace#22
• Exclude unnecessary files from the npm package by @​pkuczynski in felixge/node-stack-trace#33
• Fix: Correctly parse paths with braces by @​timfish in felixge/node-stack-trace#32
• Feature/esm jest by @​niemyjski in felixge/node-stack-trace#35
• Adjust node engine requirements to be less restrictive by @​mweichert in felixge/node-stack-trace#39
• fix(tests): make stack frame comparison test environment-independent for Jest 30 upgrade by @​niemyjski in felixge/node-stack-trace#65
• Migrate tests to native node:test, remove Babel/Jest tooling, and clarify long-stack-trace behavior by @​niemyjski in felixge/node-stack-trace#66
• Address PR #66 review comments, verify and close issues #13, #25 by @​niemyjski in felixge/node-stack-trace#67

New Contributors

• @​DylanTackoor made their first contribution in felixge/node-stack-trace#28
• @​mightyiam made their first contribution in felixge/node-stack-trace#24
• @​pkuczynski made their first contribution in felixge/node-stack-trace#33
• @​timfish made their first contribution in felixge/node-stack-trace#32
• @​niemyjski made their first contribution in felixge/node-stack-trace#35
• @​mweichert made their first contribution in felixge/node-stack-trace#39
• @​dependabot[bot] made their first contribution in felixge/node-stack-trace#43
• @​gameroman made their first contribution in felixge/node-stack-trace#58

Full Changelog: felixge/node-stack-trace@v0.0.10...v1.0.0

1.0.0-pre2

What's Changed

• Adjust node engine requirements to be less restrictive by @​mweichert in felixge/node-stack-trace#39

New Contributors

• @​mweichert made their first contribution in felixge/node-stack-trace#39

Full Changelog: felixge/node-stack-trace@1.0.0-pre1...1.0.0-pre2

1.0.0-pre1

What's Changed

• Don't expect column number to always exists by @​kjg in felixge/node-stack-trace#17
• Add Travis CI by @​kjg in felixge/node-stack-trace#18
• Updated CallSite object API link by @​DylanTackoor in felixge/node-stack-trace#28
• test on Node.js 8 by @​mightyiam in felixge/node-stack-trace#24
• fix test-long-stack-trace.js by @​mightyiam in felixge/node-stack-trace#23
• use npm scripts instead of Makefile by @​mightyiam in felixge/node-stack-trace#22
• Exclude unnecessary files from the npm package by @​pkuczynski in felixge/node-stack-trace#33
• Fix: Correctly parse paths with braces by @​timfish in felixge/node-stack-trace#32
• Feature/esm jest by @​niemyjski in felixge/node-stack-trace#35

New Contributors

• @​kjg made their first contribution in felixge/node-stack-trace#17

... (truncated)

Commits

• 68ba537 bump version
• dc0109b Address PR #66 review comments, verify and close issues #13, #25 (#67)
• e19d06c Migrate tests to native node:test, remove Babel/Jest tooling, and clarify lon...
• 2f11520 fix(tests): make stack frame comparison test environment-independent for Jest...
• 5b67838 Fixed lock file
• dabeee2 chore: migrate from Travis CI to GitHub Actions
• 1d6b4c7 Fixed url
• 5933e73 chore: update .npmignore (#58)
• 6afc300 Bump minimatch from 3.0.4 to 3.1.2 (#43)
• ba06dcd Adjust node engine requirements to be less restrictive (#39)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by niemyjski, a new releaser for stack-trace since your current version.

[TheRealAgentK]

Closing this automated major-version update intentionally after runtime compatibility review.

stack-trace 1.0.0 is not compatible with the current Raygun4Node package contract:

• Version 1.0.0 is ESM-only ("type": "module"), while Raygun4Node is compiled and published as CommonJS.
• Version 1.0.0 requires Node.js >=20.0.0, while Raygun4Node declares support for Node.js >=14.17.0.
• The full Raygun4Node test suite passes on the proposed update, but the dedicated CommonJS consumer test fails on Node 20, 22, and 24 because the compiled SDK attempts to require() the ESM-only dependency.
• AWS Lambda consumes Raygun4Node through CommonJS, so merging this update would also risk breaking the Lambda provider and downstream CommonJS applications.
• The currently pinned stack-trace 0.0.10 release has no npm audit vulnerability, so there is no security justification for accepting this compatibility regression.

A future major-version dependency replacement or module-format migration must be handled as deliberate product work, with an approved Node support floor, CommonJS/ESM strategy, packed-package consumer testing, and coordinated AWS Lambda validation. It must not be applied as an automated dependency-only update.

@dependabot ignore this major version

[dependabot]

OK, I won't notify you about version 1.x.x again, unless you re-open this PR.

[TheRealAgentK]

Long-term remediation is now tracked in #539. That issue records the compatibility policy decisions, replacement strategies, parser fidelity fixtures, CommonJS packaging tests, AWS Lambda validation, and release criteria required to remove the legacy dependency safely.