Skip to content

chromium: Update to 132 #865

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

Closed
adalessandro opened this issue Jan 6, 2025 · 4 comments · Fixed by #867
Closed

chromium: Update to 132 #865

adalessandro opened this issue Jan 6, 2025 · 4 comments · Fixed by #867

Comments

@adalessandro
Copy link
Contributor

@MaxIhlenfeldt opening this one as an RFC mainly.

  • Is there a plan to update to chromium 132? Or is this recipe targeting stable versions?
@MaxIhlenfeldt
Copy link
Collaborator

We're only targeting stable versions.

@adalessandro
Copy link
Contributor Author

We're only targeting stable versions.

@MaxIhlenfeldt as 132 is about to be stable release AFAIU, would you mind if I push a PR for the upgrade? I already have it ported and would be glad to iterate on that if you're available to review it. Let me know :-)

@MaxIhlenfeldt
Copy link
Collaborator

Sure, I'd be happy to review!

@adalessandro
Copy link
Contributor Author

adalessandro commented Jan 15, 2025

Okay - will push something ASAP updating to:
https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_14.html

adalessandro added a commit to adalessandro/meta-browser that referenced this issue Jan 21, 2025
adalessandro added a commit to adalessandro/meta-browser that referenced this issue Jan 22, 2025
adalessandro added a commit to adalessandro/meta-browser that referenced this issue Jan 28, 2025
adalessandro added a commit to adalessandro/meta-browser that referenced this issue Jan 30, 2025
adalessandro added a commit to adalessandro/meta-browser that referenced this issue Feb 11, 2025
@MaxIhlenfeldt MaxIhlenfeldt linked a pull request Feb 20, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants