Skip to content

ci: enforce synchronized uv lockfile - #185

Open
abhinavkr26104 wants to merge 1 commit into
browserbase:mainfrom
abhinavkr26104:fix/issue-177-lockfile-ci
Open

ci: enforce synchronized uv lockfile#185
abhinavkr26104 wants to merge 1 commit into
browserbase:mainfrom
abhinavkr26104:fix/issue-177-lockfile-ci

Conversation

@abhinavkr26104

Copy link
Copy Markdown

Summary

  • regenerate uv.lock for browserbase 1.17.0 and the current development dependencies
  • regenerate requirements-dev.lock from the synchronized resolution
  • pin CI to uv 0.12.3 and require locked installs / an explicit lockfile check

Why

The committed lockfile still described browserbase 1.15.0 and omitted the Playwright, Selenium, and related development dependency graph declared in pyproject.toml. Contributor bootstrap therefore changed tracked files, while reproducible installs omitted declared tooling.

Fixes #177

Testing

Known baseline: mypy on Python 3.12 reports the existing TypeAliasType incompatibility tracked in #178. A Python 3.9 Windows all-extras install also reaches the newly locked Playwright graph but cannot build greenlet 3.2.5 in this local machine because the Windows SDK headers are unavailable; the supported Linux CI job validates the project bootstrap.

@socket-security

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedplaywright@​1.60.07910010010080
Addedselenium@​4.36.091100100100100
Addedpython-dotenv@​1.2.19999100100100
Addedpytest-playwright@​0.7.1100100100100100

View full report

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: pypi pycparser is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/selenium@4.47.0pypi/selenium@4.36.0pypi/pycparser@3.0

ℹ Read more on: This package | This alert | What is obfuscated code?

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 support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pycparser@3.0. 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.

Warn High
Obfuscated code: pypi pycparser is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/selenium@4.47.0pypi/selenium@4.36.0pypi/pycparser@3.0

ℹ Read more on: This package | This alert | What is obfuscated code?

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 support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pycparser@3.0. 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

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.

Regenerate stale uv.lock and enforce lockfile consistency in CI

1 participant