-
Notifications
You must be signed in to change notification settings - Fork 824
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
Merge up from 4 to 5 #10651
Merge up from 4 to 5 #10651
Conversation
….11/cve-2022-38724-embed-shortcode Restrict embed shortcode attributes
….11/cve-2022-38462 Don't allow CRLF in header values
….11/cve-2022-37430 Sanitise mixed case javascript
….10/cve-2022-38148 Validate SortColumn exists
…pulls/runtemplate-fix
…rstripe#10593) Co-authored-by: Michal Kleiner <[email protected]>
* ENH: saveInto() new extension points.
…/deprecate-html5 API Deprecate HTML4Value
/** | ||
* Sanitise header values to avoid possible XSS vectors | ||
*/ | ||
private function sanitiseHeader(string $value): string |
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 method is new from 4 and was conflicting with the strongly typed parameters of redirect in 5
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.
Deprecation notice in HTML4Value and HTML4ValueTest were conflicting with the removal of those files in 5.
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.
@@ -16,6 +16,7 @@ | |||
use SilverStripe\View\Parsers\ShortcodeHandler; | |||
use SilverStripe\View\Parsers\ShortcodeParser; | |||
use SilverStripe\Control\Director; | |||
use SilverStripe\Core\Config\Configurable; |
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.
There was a use use SilverStripe\Dev\Deprecation;
statement here that was causing a conflict.
You mention |
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.
I got the same results when doing a local merge up so this looks good to me. For what it's worth, the conflicts were very small, I'd have been comfortable with that being merged and pushed without a PR.
Just did a merge up from the 4 branch to the 5 branch.
Normally I would just push directly to the branch, but there's enough merge conflicts to resolve that it's probably worth doing an actual peer review.
The following files had conflicts.