Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deps: Update dependency mssql to v10 #260

Merged
merged 2 commits into from
Jan 17, 2024

Conversation

renovate-bot
Copy link
Contributor

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mssql ^9.3.2 -> ^10.0.0 age adoption passing confidence

Release Notes

tediousjs/node-mssql (mssql)

v10.0.1

Compare Source

Performance Improvements
  • use node: prefix to bypass require.cache call for builtins (145d562)

v10.0.0

Compare Source

[change] Upgrade tedious to v16 (#​1547)
[removed] Removed NodeJS 14 support (#​1547)


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

forking-renovate bot commented Nov 24, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: typeorm@0.3.17
npm ERR! Found: mssql@10.0.1
npm ERR! node_modules/mssql
npm ERR!   dev mssql@"^10.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional mssql@"^9.1.1" from typeorm@0.3.17
npm ERR! node_modules/typeorm
npm ERR!   dev typeorm@"^0.3.17" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: mssql@9.3.2
npm ERR! node_modules/mssql
npm ERR!   peerOptional mssql@"^9.1.1" from typeorm@0.3.17
npm ERR!   node_modules/typeorm
npm ERR!     dev typeorm@"^0.3.17" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2023-12-13T17_46_01_777Z-debug-0.log

@renovate-bot renovate-bot requested a review from a team as a code owner November 24, 2023 16:42
@ruyadorno ruyadorno merged commit 6374582 into GoogleCloudPlatform:main Jan 17, 2024
36 checks passed
ruyadorno added a commit that referenced this pull request Jan 25, 2024
Now that an updated version of `mssql` >= 10 has landed, we no longer
need the specifier override used for pinning `tedious` in our
`package.json` file.

Refs: #260
Refs: #154
ruyadorno added a commit that referenced this pull request Jan 25, 2024
Now that an updated version of `mssql` >= 10 has landed, we no longer
need the specifier override used for pinning `tedious` in our
`package.json` file.

Refs: #260
Refs: #154
ruyadorno added a commit that referenced this pull request Jan 25, 2024
Now that an updated version of `mssql` >= 10 has landed, we no longer
need the specifier override used for pinning `tedious` in our
`package.json` file.

Refs: #260
Refs: #154
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