contracts-wizard icon indicating copy to clipboard operation
contracts-wizard copied to clipboard

Published 20 hours ago • verified publisher icon OpenZeppelin

Update dependency @upstash/redis to v1.35.0

Open renovate[bot] opened this issue 7 months ago • 1 comments

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@upstash/redis 1.25.2 -> 1.35.0 age adoption passing confidence

Release Notes

upstash/upstash-redis (@​upstash/redis)

v1.35.0

Compare Source

What's Changed

Features:

Fixes:

Full Changelog: https://github.com/upstash/redis-js/compare/v1.34.9...v1.35.0

v1.34.9

Compare Source

What's Changed

Fixes:

Full Changelog: https://github.com/upstash/redis-js/compare/v1.34.8...v1.34.9

v1.34.8

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/redis-js/compare/v1.34.7...v1.34.8

v1.34.7

Compare Source

What's Changed

Features:

Fixes:

Full Changelog: https://github.com/upstash/redis-js/compare/v1.34.6...v1.34.7

v1.34.6

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/upstash/redis-js/compare/v1.34.5...v1.34.6

v1.34.5

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/redis-js/compare/v1.34.4...v1.34.5

v1.34.4

Compare Source

What's Changed

Features:

Fixes:

New Contributors

Full Changelog: https://github.com/upstash/redis-js/compare/v1.34.3...v1.34.4

v1.34.3

Compare Source

What's Changed

Changes

Vercel Env Variables

@​upstash/redis sdk now also works when the env variables of Vercel KV are set:

KV_REST_API_URL
KV_REST_API_TOKEN
Granular Auto Pipeline Errors

When the pipeline of the auto pipeline failed, it threw an error for all commands in the auto pipeline. This is not ideal for the use case of auto pipeline. Now, they are raised seperately.

This required changing the exec method of Pipeline. It's not possible to return the errors instead of raising them. See the docstring for more details.

Remove throw on missing URL/Token

We updated the SDK to throw error if the URL or the token is not set in v1.31.1, in PR #​1065. This causes the Vercel builds in Turbo repo to fail unless the turbo.json is updated.

Now, we only print warning logs if the credentials are missing, instead of throwing.

Full Changelog: https://github.com/upstash/redis-js/compare/v1.34.2...v1.34.3

v1.34.2

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/redis-js/compare/v1.34.1...v1.34.2

v1.34.1

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/upstash/redis-js/compare/v1.34.0...v1.34.1

v1.34.0

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/redis-js/compare/v1.33.0...v1.34.0

v1.33.0

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/redis-js/compare/v1.32.0...v1.33.0

v1.32.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/upstash/redis-js/compare/v1.31.6...v1.32.0

v1.31.6

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/redis-js/compare/v1.31.5...v1.31.6

v1.31.5

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/redis-js/compare/v1.31.4...v1.31.5

v1.31.4

Compare Source

What's Changed

After this patch, cursor field in the SCAN, HSCAN, SSCAN and ZSCAN will always be string even if deserialization is enabled.

Full Changelog: https://github.com/upstash/redis-js/compare/v1.31.3...v1.31.4

v1.31.3

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/redis-js/compare/v1.31.2...v1.31.3

v1.31.2

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/redis-js/compare/v1.31.1...v1.31.2

v1.31.1

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/upstash/redis-js/compare/v1.31.0...v1.31.1

v1.31.0

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.30.1...v1.31.0

v1.30.1

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.30.0...v1.30.1

v1.30.0

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.29.0...v1.30.0

v1.29.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.28.4...v1.29.0

v1.28.4

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.28.3...v1.28.4

v1.28.3

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.28.2...v1.28.3

  • Added generics for JSONMGet and JSONGet
  • Run formatter for the entire project
  • Add husky for hooks

v1.28.2

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.28.1...v1.28.2

v1.28.1

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.28.0...v1.28.1

v1.28.0

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.27.1...v1.28.0

v1.27.1

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.27.0...v1.27.1

v1.27.0

Compare Source

What's Changed

Full Changelog: https://github.com/upstash/upstash-redis/compare/v1.26.0...v1.27.0

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 was generated by Mend Renovate. View the repository job log.

renovate[bot] avatar Apr 09 '25 20:04 renovate[bot]

[!CAUTION] Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block High
[email protected] has a High CVE.

CVE: GHSA-xq7p-g2vc-g82p Homograph attack allows Unicode lookalike characters to bypass validation. (HIGH)

Affected versions: = 5.0.0, 4.0.0; >= 5.0.0 < 5.0.1; >= 4.0.0 < 4.0.1; < 3.0.11

Patched version: 3.0.11

From: packages/core/solidity/src/environments/hardhat/upgradeable/package-lock.json → npm/@openzeppelin/[email protected] → npm/@nomicfoundation/[email protected] → npm/[email protected]

ℹ Read more on: This package | This alert | What is a CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Low
[email protected] is a AI-detected potential code anomaly.

Notes: The analyzed code appears to implement a standard in-memory cache batch operation flow (put/delete) with careful handling of response bodies by buffering and storing bytes for caching. No signs of malware, data exfiltration, backdoors, or obfuscated behavior were found. The primary security considerations relate to memory usage from buffering potentially large response bodies and ensuring robust validation within batch operations to prevent cache state corruption. Overall risk is moderate, driven by in-memory data handling rather than external communication.

Confidence: 1.00

Severity: 0.60

From: packages/core/solidity/src/environments/hardhat/upgradeable/package-lock.json → npm/@openzeppelin/[email protected] → npm/[email protected]

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

socket-security[bot] avatar Jul 01 '25 11:07 socket-security[bot]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Added@​openzeppelin/​hardhat-upgrades@​3.9.19910010089100
Added@​openzeppelin/​contracts-upgradeable@​5.4.010010010094100

View full report

socket-security[bot] avatar Aug 04 '25 13:08 socket-security[bot]

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

coderabbitai[bot] avatar Aug 13 '25 14:08 coderabbitai[bot]