-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
chore: update changelog #22481
chore: update changelog #22481
Conversation
332f567
to
127f05e
Compare
127f05e
to
6303146
Compare
Codecov Report
@@ Coverage Diff @@
## 2.0 #22481 +/- ##
=======================================
Coverage 66.74% 66.74%
=======================================
Files 1740 1740
Lines 65408 65408
Branches 6926 6926
=======================================
Hits 43654 43654
Misses 19981 19981
Partials 1773 1773
Flags with carried forward coverage won't be shown. Click here to find out more. 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
UPDATING.md
Outdated
@@ -22,16 +22,33 @@ under the License. | |||
This file documents any backwards-incompatible changes in Superset and | |||
assists people when migrating to a new version. | |||
|
|||
## 2.0.1 | |||
## Next |
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.
we shouldn't have a next in the 2.0 branch, but we'll have this in master. I think you'll want to create two different PRs.
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.
Ok already merged one with next into master. Should I just deleted next here?
UPDATING.md
Outdated
### Other | ||
|
||
## 2.0.1 | ||
- [21895](https://github.com/apache/superset/pull/21895): Markdown components had their security increased by adhering to the same sanitization process enforced by Github. This means that some HTML elements found in markdowns are not allowed anymore due to the security risks they impose. If you're deploying Superset in a trusted environment and wish to use some of the blocked elements, then you can use the HTML_SANITIZATION_SCHEMA_EXTENSIONS configuration to extend the default sanitization schema. There's also the option to disable HTML sanitization using the HTML_SANITIZATION configuration but we do not recommend this approach because of the security risks. Given the provided configurations, we don't view the improved sanitization as a breaking change but as a security patch. |
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 can go under other
UPDATING.md
Outdated
@@ -24,14 +24,31 @@ assists people when migrating to a new version. | |||
|
|||
## 2.0.1 | |||
|
|||
- [21895](https://github.com/apache/superset/pull/21895): Markdown components had their security increased by adhering to the same sanitization process enforced by Github. This means that some HTML elements found in markdowns are not allowed anymore due to the security risks they impose. If you're deploying Superset in a trusted environment and wish to use some of the blocked elements, then you can use the HTML_SANITIZATION_SCHEMA_EXTENSIONS configuration to extend the default sanitization schema. There's also the option to disable HTML sanitization using the HTML_SANITIZATION configuration but we do not recommend this approach because of the security risks. Given the provided configurations, we don't view the improved sanitization as a breaking change but as a security patch. | |||
- [22022](https://github.com/apache/superset/pull/22022): HTTP API endpoints `/superset/approve` and `/superset/request_access` have been deprecated and their HTTP methods were changed from GET to POST |
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 whole 2.0.1 section should be deleted.
31a6521
to
72b8463
Compare
72b8463
to
628fbf9
Compare
Co-authored-by: Elizabeth Thompson <[email protected]>
SUMMARY
making sure 2.0 branch has a changelog that accurately reflects what's happening.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION