-
Notifications
You must be signed in to change notification settings - Fork 74
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
fix(ses): reject unsupported lockdownOptions mathTaming + dateTaming #2583
Conversation
@kriskowal unrelated playwright install issue (?) |
Definitely unrelated. We saw this once before when one of the browsers shifted underneath us. I reran the job and it persisted. It’s not a required job. |
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.
This is a breaking change. We should use a console warning instead, and leave a note somewhere for behaviors we would change to errors in the next-breaking version, maybe next year.
@kriskowal whats the process for queueing breaking changes? |
2012626
to
4beaf23
Compare
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.
Is it unacceptable to just ignore the options?
EDIT:
My personal opinion is that this should not throw, because shipping a breaking change should be a last resort.
We do not have one yet, but I think a new label Closing in favor of #2584 |
This is a breaking change.
support for lockdown options
mathTaming
anddateTaming
were removed so long ago I'm having trouble finding a proper reference (edit: july 2020 #372). Since these options don't do anything, lockdown should fail when these options are specified.For LavaMoat, we were surprised to find they were being provided to lockdown, but had no effect. Any other unrecognized lockdown options are rejected.
Here is a non-breaking change that adds a warning when the options are specified #2584