chore: add latest chromium version #6952
Merged
Conversation
This file contains 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
Sync my fork with original repo
theDavidBarton
changed the title
mathiasbynens
approved these changes
Mar 4, 2021
|
Looks like I have missed that step. Thanks for fixing this! |
|
I have an opened pr (puppeteer/pptr.dev#22) that is related to rolling-new-chromium-version. The problem is pptr.dev fails to parse the Chromium version rolls anymore as the format of these announcements has changed over time in the release notes. The issue is explained in puppeteer/pptr.dev#20. @mathiasbynens do you see any chance that the pull requests on puppeteer/pptr.dev will be reviewed in the near future? I plan to make a suggestion to CONTRIBUTING.md in a pr soon, so the versions would be displayed properly on the docs site. But poor pptr.dev is an orphan child at the moment 😅 hope it will get an update sometime 😃 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In v8.0.0 the Chromium roll to r856583 was not registered to
docs/api.mdandversions.js.Now it is done retrospectively.
Follow up to: #6927