⬆️ Bump browserslist from 4.16.3 to 4.16.6#356
Merged
Conversation
Contributor
|
@dependabot rebase |
247b2d6 to
f14cf2b
Compare
Bumps [browserslist](https://github.com/browserslist/browserslist) from 4.16.3 to 4.16.6. - [Release notes](https://github.com/browserslist/browserslist/releases) - [Changelog](https://github.com/browserslist/browserslist/blob/main/CHANGELOG.md) - [Commits](browserslist/browserslist@4.16.3...4.16.6) Signed-off-by: dependabot[bot] <support@github.com>
f14cf2b to
5fd0f76
Compare
samarsault
pushed a commit
that referenced
this pull request
Mar 3, 2023
Bumps [tsd](https://github.com/SamVerschueren/tsd) from 0.16.0 to 0.17.0. - [Release notes](https://github.com/SamVerschueren/tsd/releases) - [Commits](tsdjs/tsd@v0.16.0...v0.17.0) --- updated-dependencies: - dependency-name: tsd dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
pranavz28
added a commit
that referenced
this pull request
Apr 22, 2026
Follow-up to the initial --max-cache-ram implementation. Previously a
value below the 25 MB MAX_RESOURCE_SIZE floor threw an error at Percy
startup, killing otherwise-healthy builds for a misconfigured cap.
Switch to a warn-level log and continue with the 25 MB minimum:
--max-cache-ram=10MB is below the 25MB minimum (individual resources
up to 25MB would otherwise be dropped). Continuing with the minimum:
25MB.
Also mutates percy.config.discovery.maxCacheRam to the clamped value so
the cache_summary telemetry event reports the effective cap.
Updates:
* discovery.js — throw → warn + clamp
* discovery.test.js — integration test asserts warn log + clamped cap
* README.md — docs reflect the clamp behaviour
* cli-command/test/flags.test.js — stale help-text fixture: inserts
the --max-cache-ram line between --disable-cache and --debug
(broken since the flag was added; unrelated to the clamp, bundled
here since both are help-surface / startup-UX fixes)
Verified in-anger with percy snapshot --max-cache-ram 10 against
https://example.com (build #356):
[percy:core] --max-cache-ram=10MB is below the 25MB minimum
(individual resources up to 25MB would otherwise be dropped).
Continuing with the minimum: 25MB.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps browserslist from 4.16.3 to 4.16.6.
Changelog
Sourced from browserslist's changelog.
Commits
6fe3614Release 4.16.6 version33ebac9Update dependencies2128170Add support for npm-shrinkwrap files alongside package-lock (#595)7cc2aedRelease 4.16.5 version27e4afdUpdate dependencies1013a18Fix version RegExpb879a1aUse Node.js 16 on CIbd1e9e0Fix ReDoS (#593)209adf9Release 4.16.4 version3e2ae3bFix typesDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.