gitscratch-frontend
gitscratch-frontend copied to clipboard
fix(deps): bump sanitize-html from 2.7.1 to 2.10.0
Bumps sanitize-html from 2.7.1 to 2.10.0.
Changelog
Sourced from sanitize-html's changelog.
2.10.0 (2023-02-17)
- Fix auto-adding escaped closing tags. In other words, do not add implied closing tags to disallowed tags when
disallowedTagModeis set to any variant ofescape-- just escape the disallowed tags that are present. This fixes [issue #464](apostrophecms/sanitize-html#464). Thanks to Daniel Liebner- Add
tagAllowed()helper function which takes a tag name and checks it againstoptions.allowedTagsand returnstrueif the tag is allowed andfalseif it is not.2.9.0 (2023-01-27)
- Add option parseStyleAttributes to skip style parsing. This fixes [issue #547](apostrophecms/sanitize-html#547). Thanks to Bert Verhelst.
2.8.1 (2022-12-21)
- If the argument is a number, convert it to a string, for backwards compatibility. Thanks to Alexander Schranz.
2.8.0 (2022-12-12)
- Upgrades
htmlparser2to new major version^8.0.0. Thanks to Kedar Chandrayan for this contribution.2.7.3 (2022-10-24)
- If allowedTags is falsy but not exactly
false, then do not assume that all tags are allowed. Rather, allow no tags in this case, to be on the safe side. This matches the existing documentation and fixes [issue #176](apostrophecms/sanitize-html#176). Thanks to Kedar Chandrayan for the fix.2.7.2 (2022-09-15)
- Closing tags must agree with opening tags. This fixes [issue #549](apostrophecms/sanitize-html#549), in which closing tags not associated with any permitted opening tag could be passed through. No known exploit exists, but it's better not to permit this. Thanks to Kedar Chandrayan for the report and the fix.
Commits
b9eb465Merge pull request #608 from apostrophecms/release-2.10.0e95ffe7release 2.10.0d5fbdc6Merge pull request #607 from dliebner/main6ea35adlintingf9b6fa5Add testse8a0f80Handle htmlparser2.onclosetag isImplied parameter1d41e4dFixing0aa5a98Fixingb08a176Fix #464f12a665Merge pull request #605 from apostrophecms/release-2.9.0- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Dependabot tried to add @TimFang4162, @Dispure, @HydroGest and @wrj2009 as reviewers to this PR, but received the following error from GitHub:
POST https://api.github.com/repos/UniScratch/gitscratch-frontend/pulls/118/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the UniScratch/gitscratch-frontend repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated |
|---|---|---|---|---|
| gitscratch-frontend | ❌ Failed (Inspect) | Feb 20, 2023 at 2:15AM (UTC) |