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

feat(chrome)!: update the pinned browser version to 135.0.7000.0 #3081

Conversation

browser-automation-bot
Copy link
Contributor

@browser-automation-bot browser-automation-bot force-pushed the browser-automation-bot/update-browser-version branch from aa29ec7 to 91ed509 Compare February 5, 2025 12:07
@sadym-chromium sadym-chromium force-pushed the browser-automation-bot/update-browser-version branch from 91ed509 to 7b274a5 Compare February 5, 2025 13:48
@browser-automation-bot browser-automation-bot force-pushed the browser-automation-bot/update-browser-version branch from 7b274a5 to 9acf97c Compare February 6, 2025 00:17
@browser-automation-bot browser-automation-bot changed the title feat(chrome)!: update the pinned browser version to 135.0.6999.0 feat(chrome)!: update the pinned browser version to 135.0.7000.0 Feb 6, 2025
@OrKoN
Copy link
Collaborator

OrKoN commented Feb 6, 2025

@sadym-chromium should we release mapper before we push a new major Chrome version?

@sadym-chromium
Copy link
Collaborator

@sadym-chromium should we release mapper before we push a new major Chrome version?

done

@sadym-chromium sadym-chromium force-pushed the browser-automation-bot/update-browser-version branch from 9acf97c to 20a8d3e Compare February 6, 2025 11:34
@sadym-chromium sadym-chromium enabled auto-merge (squash) February 6, 2025 11:34
@sadym-chromium sadym-chromium merged commit 6061a41 into GoogleChromeLabs:main Feb 6, 2025
47 checks passed
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.

3 participants