-
Notifications
You must be signed in to change notification settings - Fork 23
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
#8343: handle 4 digit extension version numbers #8346
#8343: handle 4 digit extension version numbers #8346
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8346 +/- ##
=======================================
Coverage 73.49% 73.50%
=======================================
Files 1330 1330
Lines 41113 41131 +18
Branches 7636 7643 +7
=======================================
+ Hits 30217 30233 +16
- Misses 10896 10898 +2 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The types continue to be super-sketchy (e.g., the "allowV" producing an invalid SemVerString). But this PR seems OK. Approving to unblock E2E testing
I ran a quick search for getManifest() and didn't spot any places where we were reading the version
When the PR is merged, the first loom link found on this PR will be posted to |
What does this PR do?
Reviewer Tips
src/types/helpers.ts
andsrc/utils/extensionUtils.ts
firstDiscussion
ExtensionsVersionString
type using a brand, but ran into too many conflicts withSemVerString
Demo
https://www.loom.com/share/a06553e9794042489c035989b2505b76
Future Work
getExtensionVersion()
tobrowser.runtime.getManifest().version
Checklist