chore: Release 2.2.5

[TheRealAgentK]

chore: Release 2.2.5

Description 📝

• Purpose: Prepare release 2.2.5 with dependency maintenance and security fixes.
• Approach: Bump version in package.json, update CHANGELOG.md, regenerate lockfiles.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Updates

👉 Version bump from 2.2.4 to 2.2.5
👉 Updated CHANGELOG.md with all changes since 2.2.4
👉 No source code changes — strictly dependency bumps and lockfile regeneration

Changes since 2.2.4

• fix: update stale example lockfiles to resolve tar vulnerability (CVE in tar <7.5.8) (fix: update stale example lockfiles to resolve tar and qs vulnerabilities #468)
• fix: update minimatch in example lock files to resolve ReDoS vulnerabilities
• chore(deps-dev): bump minimatch from 3.1.2 to 3.1.5 (chore(deps-dev): bump minimatch from 3.1.2 to 3.1.5 #469)
• chore(deps-dev): bump @types/node from 25.1.0 to 25.3.3 (chore(deps-dev): bump @types/node from 25.1.0 to 25.3.3 #471)
• chore(deps-dev): bump semver from 7.7.3 to 7.7.4 (chore(deps-dev): bump semver from 7.7.3 to 7.7.4 #472)
• chore(deps-dev): bump eslint-plugin-tsdoc from 0.5.0 to 0.5.2 (chore(deps-dev): bump eslint-plugin-tsdoc from 0.5.0 to 0.5.2 #474)
• chore(deps): bump config from 4.2.0 to 4.4.1 in /examples/express-sample (chore(deps): bump config from 4.2.0 to 4.4.1 in /examples/express-sample #476)
• chore(deps): bump config from 4.2.0 to 4.4.1 in /examples/using-domains (chore(deps): bump config from 4.2.0 to 4.4.1 in /examples/using-domains #477)
• chore: regenerate lockfiles to resolve transitive vulnerabilities (chore: regenerate lockfiles to resolve transitive vulnerabilities #478)

Test plan 🧪

• npm test — all 258 tests pass
• npm run eslint / npm run tseslint — clean
• npm audit — 0 vulnerabilities (root and both examples)
• npm publish --dry-run — clean

Author to check 👓

• Project and all contained modules builds successfully
• Self-/dev-tested
• Unit/UI/Automation/Integration tests provided where applicable
• Code is written to standards
• Appropriate documentation written (code comments, internal docs)

Reviewer to check ✔️

• Project and all contained modules builds successfully
• Change has been dev-/reviewer-tested, where possible
• Unit/UI/Automation/Integration tests provided where applicable
• Code is written to standards
• Appropriate documentation written (code comments, internal docs)

[Copilot]

Pull request overview

Prepares the 2.2.5 release of the Raygun Node.js/TypeScript package by updating the published version metadata and documenting release notes, alongside the corresponding root lockfile version update.

Changes:

• Bump package version from 2.2.4 → 2.2.5 in package.json.
• Update root package-lock.json package version metadata to 2.2.5.
• Add a 2.2.5 section to CHANGELOG.md summarizing changes since 2.2.4.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
package.json	Updates the package version to 2.2.5 for the release.
package-lock.json	Updates root lockfile package version metadata to 2.2.5.
CHANGELOG.md	Adds release notes for 2.2.5.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ProRedCat]

Lgtm, would be good for @miquelbeltran to take a look over this too though :)