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

build(deps): bump vercel from 25.2.3 to 28.16.13 #128

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Mar 7, 2023

Bumps vercel from 25.2.3 to 28.16.13.

Release notes

Sourced from vercel's releases.

[email protected]

tests

  • [tests] Upgrade Turbo to version 1.8.3 (#9604) [Vercel Release Bot]
  • [tests] Add more remix tests (#9600) [Ethan Arrowood]

next

  • [next] Fix api prefixed app routes serverless streaming (#9603) [JJ Kasper]

remix

  • [remix] Add test for escaped route paths (#9516) [Nathan Rajlich]
  • [remix] Clean up dev symlink upon config error (#9595) [Nathan Rajlich]
  • [remix] Return framework.version in build result (#9596) [Nathan Rajlich]
  • [remix] Fix support for optional path params (#9590) [Nathan Rajlich]
  • [remix] Upgrade @​remix-run/dev to version 1.14.0 (#9593) [Vercel Release Bot]
  • [remix] Fix remix updater workflow when fetching latest version (#9592) [Ethan Arrowood]

cli

  • [cli] change patch-inquirer-legacy to patch-inquirer (#8919) [Jeemin Choi(최지민)]

examples

  • [examples] Run prettier on Remix template (#9594) [Nathan Rajlich]

[email protected]

remix

  • [remix] Make symlink logic of @remix-run/dev work in monorepos (#9591) [Nathan Rajlich]

[email protected]

remix

  • [remix] Upgrade @remix-run/dev to v1.13.0-patch.2 (#9589) [Vercel Release Bot]
  • [remix] Add better error message when server build directory is missing (#9584) [Nathan Rajlich]
  • [remix] Support "regions", "memory" and "maxDuration" in static config (#9442) [Nathan Rajlich]
  • [remix] Split Edge and Node server builds using serverBundles config (#9504) [Nathan Rajlich]

examples

  • [examples] Upgrade Next.js to version 13.2.3 (#9586) [Vercel Release Bot]

next

  • [next] Fix incorrect 404 when i18n and appDir configured (#9582) [Steven]

[email protected]

remix

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [vercel](https://github.com/vercel/vercel/tree/HEAD/packages/cli) from 25.2.3 to 28.16.13.
- [Release notes](https://github.com/vercel/vercel/releases)
- [Commits](https://github.com/vercel/vercel/commits/[email protected]/packages/cli)

---
updated-dependencies:
- dependency-name: vercel
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 7, 2023
@vercel
Copy link

vercel bot commented Mar 7, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
dgiot-doc ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Mar 7, 2023 at 2:09AM (UTC)

@pull-request-quantifier-deprecated

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file Extra Small
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants