Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 12, 2025

This PR contains the following updates:

Package Type Update Change OpenSSF
semver overrides patch 7.7.1 -> 7.7.2 OpenSSF Scorecard

Release Notes

npm/node-semver (semver)

v7.7.2

Compare Source

Bug Fixes
Chores

Configuration

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

🚦 Automerge: Enabled.

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.

Summary by Sourcery

Update semver override to v7.7.2 to include the latest patch fixes.

Bug Fixes:

  • Add missing 'use strict' directives in semver module
  • Allow numeric prerelease identifiers in semver parsing

Chores:

  • Bump semver override from v7.7.1 to v7.7.2

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot enabled auto-merge (squash) May 12, 2025 17:56
@sourcery-ai
Copy link

sourcery-ai bot commented May 12, 2025

Reviewer's Guide

Upgrade semver from v7.7.1 to v7.7.2 by bumping the version in package.json and regenerating the lockfile to incorporate the patch release.

File-Level Changes

Change Details Files
Dependency update for semver to incorporate the latest bug fixes
  • Updated semver version spec from 7.7.1 to 7.7.2
  • Regenerated bun.lock to reflect the new semver version
package.json
bun.lock

Possibly linked issues

  • #0: PR updates semver dependency, which is tracked and listed as an open update in the issue's dashboard.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@github-actions
Copy link

📦 Packages

Package Install
Template Set bun add @settlemint/settlemint/solidity-token-erc721a@8.0.9-pr7d34d4e

@renovate renovate bot merged commit e2ae79c into main May 12, 2025
3 checks passed
@renovate renovate bot deleted the renovate/semver-7.x branch May 12, 2025 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant