-
Notifications
You must be signed in to change notification settings - Fork 17
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
Always build HTTPSE with the latest rulesets, fix #7 #12
Conversation
throw err | ||
} else { | ||
let timestamp = '' | ||
let baseURL = 'https://www.https-rulesets.org/v1/' |
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.
does EFF guarantee that the rulesets published under v1
will be compatible with HTTPSE'2018.9.19'
? i assume so but just checking because they've done a few updates in the past where the format has changed (and so auto-updating would have broken Brave).
otherwise this approach looks great
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 v1
directory was added as per EFForg/https-everywhere#14907 (comment) and EFForg/https-everywhere#14907 (comment), so I assume there shouldn't be breaking changes in the rulesets format. Maybe @Hainish @zoracon from EFF can help guarantee that?
@bsclifton when you get a chance, please merge this and upload the new HTTPS Everywhere rulesets. Thanks |
There is no need to bump the XPI version number anymore.
No description provided.