Skip to content

chore(deps): upgraded to latest dependencies#162

Open
vinaygupta-sourcefuse wants to merge 3 commits intomasterfrom
GH-161
Open

chore(deps): upgraded to latest dependencies#162
vinaygupta-sourcefuse wants to merge 3 commits intomasterfrom
GH-161

Conversation

@vinaygupta-sourcefuse
Copy link
Copy Markdown
Collaborator

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
  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style guide
  • API Documentation in code was updated
  • Any dependent changes have been merged and published in downstream modules

Build Passed:

Screenshot 2026-04-10 at 11 39 12 AM

Test Passed:

Screenshot 2026-04-10 at 11 39 52 AM

@vinaygupta-sourcefuse vinaygupta-sourcefuse self-assigned this Apr 10, 2026
upgraded to latest dependencies

GH-161
Comment thread src/providers/authorization-metadata.provider.ts
Comment thread package.json Outdated
"fs-extra": "^11.3.4",
"git-release-notes": "^5.0.0",
"husky": "^7.0.4",
"jsdom": "^21.0.0",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

jsdom

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'll update this in follow-up PR since it is a major version change.

Comment thread package.json Outdated
Comment on lines 58 to 71
"@loopback/boot": "^8.0.11",
"@loopback/build": "^12.0.10",
"@loopback/context": "^8.0.10",
"@loopback/eslint-config": "^16.0.1",
"@loopback/rest": "^15.0.4",
"@loopback/testlab": "^8.0.3",
"@semantic-release/changelog": "^6.0.1",
"@loopback/rest": "^15.0.11",
"@loopback/testlab": "^8.0.10",
"@semantic-release/changelog": "^6.0.3",
"@semantic-release/commit-analyzer": "^9.0.2",
"@semantic-release/git": "^10.0.1",
"@semantic-release/github": "^12.0.0",
"@semantic-release/npm": "^13.1.1",
"@semantic-release/github": "^12.0.6",
"@semantic-release/npm": "^13.1.5",
"@semantic-release/release-notes-generator": "^10.0.3",
"@types/lodash": "^4.14.181",
"@types/lodash": "^4.17.24",
"@types/node": "^18.11.9",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please keep the packages at the same version in all the extensions
the versions @semantic-release packages look diff in all the extensions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@semantic-release/release-notes-generator

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should i need to revert versions of all @semantic-release/ and what about
@semantic-release/release-notes-generator, need little clarification.

upgraded to latest dependencies, comment resolved

Gh-161
@sonarqubecloud
Copy link
Copy Markdown

SonarQube reviewer guide

Summary: Dependency updates and minor code formatting improvements across the project.

Review Focus:

  • Significant version bumps in key security/feature dependencies: casbin (5.32.0 → 5.49.0), @loopback/* packages, and dev dependencies like @semantic-release/*
  • Minor code formatting changes (line breaks in class declarations) that shouldn't affect functionality
  • Updated Trivy action to a specific commit hash with version tag

Start review at: package.json. This file captures all the meaningful changes - the dependency updates represent the core of this PR. The code formatting changes in the provider files are cosmetic and follow consistent patterns, so reviewing package.json first will identify what actually changed and whether those versions are compatible with the codebase.

💬 Please send your feedback

Quality Gate Passed 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants