chore(deps): upgraded to latest dependencies

[Sourav-kashyap]

Description

This issue tracks upgrading all project dependencies to their latest stable versions.

Changes

• Updated all dependencies and devDependencies to latest versions
• Resolved version conflicts and peer dependency issues
• Fixed breaking changes introduced by major version upgrades

Checklist:

• Performed a self-review of my own code
• npm test passes on your machine

Build Passed:

Test Passed:

[sonarqubecloud]

SonarQube reviewer guide

Summary: Update GitHub Actions versions (checkout@v4, setup-node@v4) and trivy-action to v0.35.0 with pinned commit hash, plus dependency upgrades across LoopBack, semantic-release, and related tooling packages.

Review Focus: Pay close attention to the Trivy action configuration change where the version pinning strategy shifted from semantic versioning (v0.28.0) to a commit hash (v0.35.0). Also verify that the upgraded semantic-release packages (@semantic-release/commit-analyzer v13, @semantic-release/release-notes-generator v14) maintain compatibility with the existing release workflow, as these are major version bumps. Check whether the loopback dependency updates are tested against peer dependencies.

Start review at: .github/workflows/trivy.yaml. This is the riskiest change in the PR, as it shifts from a semantic version to a pinned commit hash and updates to a newer major version of trivy-action. This could affect security scanning behavior and CI/CD reliability, so it warrants careful scrutiny of what changed in those versions.

💬 Please send your feedback

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud