build(deps): update xss requirement from ^1.0.14 to ^1.0.15 in /superset-frontend/plugins/plugin-chart-table

[dependabot]

Updates the requirements on xss to permit the latest version.

Changelog

Sourced from xss's changelog.

v1.0.15 (2024-03-03)

• feat: add <kbd> to default whitelist by @​rayrny
• feat: single-quoted attribute value syntax support by @​mdk000

v1.0.14 (2022-08-16)

• fix: problem with not closed tag by @​slawiko
• fix: add allowList to types by @​metonym

v1.0.13 (2022-06-07)

• revert: fix: comment has encoded

v1.0.12 (2022-06-04)

• feat: add eslint:recommended check by @​lumburr
• fix: comment has encoded by @​lumburr
• fix: whitelist match failure due to case ignoring by @​lumburr
• fix: class is wrong separated by attributes in method onTagAttr by @​lumburr

v1.0.11 (2022-03-06)

• feat: add support for allowList as an alias for whiteList by @​schu34

v1.0.10 (2021-10-08)

• [Fix: #239 stripCommentTag DoS attack](leizongmin/js-xss#239)

v1.0.9 (2021-05-06)

• [Fix whitespace bypass #218](leizongmin/js-xss#218) by @​TomAnthony
• [Add <summary> to default whitelist #216](leizongmin/js-xss#216) by @​spacegaier
• Add <figure> and <figcaption> to default whitelist by @​daraz999
• Add <audio crossorigin muted>, <video crossorigin muted playsinline poster> to default whitelist
• Add <strike> to default whitelist
• Fix: typings IWhiteList allow any tag name
• Fix: typings onTag options

v1.0.8 (2020-07-27)

• [Allow default imports in TS #200](leizongmin/js-xss#200) by @​danvk
• [Update handling of quoteStart to prevent sanitization bypass #201](leizongmin/js-xss#201) by @​TomAnthony

v1.0.7 (2020-06-08)

• added support for src embedded image, ftp and relative urls by @​sijanec

Commits

• 9c92272 publish: v1.0.15
• ae15483 feat: add <kbd> to default whitelist (#279)
• bedb0c0 feat: single-quoted attribute value syntax support (#287)
• 8884b21 feat: Allow loading attribute on img (#278)
• 4c3c758 chore: fix typo (#272)
• See full diff 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[rusackas]

@mistercrunch I'm still stumped why the actions don't have permissions to push to the branch. Curious if you have any theories.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[mistercrunch]

@mistercrunch I'm still stumped why the actions don't have permissions to push to the branch. Curious if you have any theories

Do you mean this? -> looks ok to me.

But in general about permissions to push to the repo you'll need something like
https://github.com/apache/superset/blob/master/.github/workflows/latest-release-tag.yml#L10-L11
and
https://github.com/apache/superset/blob/master/.github/workflows/latest-release-tag.yml#L36-L37

[mistercrunch]

For the record here I forced rebased the damn thing, not sure what was wrong with it prior to that

[rusackas]

It seems for some reason like the action can't push the commit until one of us humanoids commits or force-pushes the thing.

Previously I was pulling the branch, doing npm install and committing a package lock. It's tedious. Not sure if supersetbot would have different or better luck with this task than this action is having.

[mistercrunch]

@rusackas this may help -> #27860