| Summary: | Figure out how to tell if a Web Extension has been updated in WebKit | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Kiara Rose <kiara_rose> |
| Component: | WebKit Extensions | Assignee: | Timothy Hatcher <timothy> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | timothy, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Local Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Kiara Rose
2022-12-13 15:29:15 PST
When developers are making local changes to their extension for testing, they're likely not changing the extension version number. One option would be the take a hash of all the files in the bundle, and if any change assume it changed One option is to check and remember the previous code signing hash. That should change everything there is a change in the bundle. Tim mentioned an idea of hashing all the files and seeing if the hash changes Pull request: https://github.com/WebKit/WebKit/pull/26778 Committed 277022@main (adf9728dc4e1): <https://commits.webkit.org/277022@main> Reviewed commits have been landed. Closing PR #26778 and removing active labels. |