Skip to content

chore(deps): lock file maintenance - #2107

Merged
vdusek merged 4 commits into
masterfrom
renovate/lock-file-maintenance
Aug 3, 2026
Merged

chore(deps): lock file maintenance#2107
vdusek merged 4 commits into
masterfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 05:59 AM, only on Monday (* 0-5 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@codecov

codecov Bot commented Aug 3, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.61%. Comparing base (acbb5a0) to head (36d2a3c).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2107      +/-   ##
==========================================
+ Coverage   93.59%   93.61%   +0.01%     
==========================================
  Files         181      181              
  Lines       12590    12590              
==========================================
+ Hits        11784    11786       +2     
+ Misses        806      804       -2     
Flag Coverage Δ
unit 93.61% <ø> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@vdusek
vdusek merged commit 463806f into master Aug 3, 2026
34 checks passed
@vdusek
vdusek deleted the renovate/lock-file-maintenance branch August 3, 2026 07:37
vdusek added a commit that referenced this pull request Aug 3, 2026
…aints are respected (#2110)

`ScreenOptions` were not respected - with `strict=True` fingerprint
generation failed, otherwise the screen
constraints were silently dropped and the fingerprint got a screen
outside of the requested range.

`browserforge` turns the screen constraints into an allow list of user
agents and passes it to the header
generator, but the generator only derives browser, operating system and
device from it and then samples the
user agent freely - so the result is often outside the list, and the
fingerprint network finds no consistent
sample. `apify-fingerprint-datapoints` 0.14.0 made that deterministic
for some inputs, hence the cap in #2107.

`PatchedHeaderGenerator` now enforces the allow list: a user agent
outside it pins the next attempt to an
allowed one with the same browser, operating system and device. If
nothing is interchangeable or the attempts
run out, the wider header is returned, so inputs that worked before keep
working.

Measured on 0.14.0, before -> after:

| Case | Before | After |
| --- | --- | --- |
| `strict` Firefox + Windows, screen `600-1800 x 400-1200` | 299/300
fail, 480 ms each | 0/500 fail, 90 ms each |
| Firefox + Android, screen `300-600 x 500-1200` | ~40% of screens out
of range | 0/2000 out of range |

Also drops the `apify-fingerprint-datapoints<0.14.0` caps from #2107.

`test_fingerprint_generator_respects_screen_options_without_strict`
covers the non-strict path; it and
`test_fingerprint_generator_all_options` fail on `master` with the
0.14.0 datapoints.

Closes: #2108

*✍️ Drafted by Claude Code*
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.

2 participants