chaibio / chaipcr

The software behind Chai's open-source Real-Time PCR instrument
https://www.chaibio.com
88 stars 36 forks source link

Bump rails-html-sanitizer from 1.0.3 to 1.4.2 in /web #57

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps rails-html-sanitizer from 1.0.3 to 1.4.2.

Release notes

Sourced from rails-html-sanitizer's releases.

1.4.2 / 2021-08-23

  • Slightly improve performance.

    Assuming elements are more common than comments, make one less method call per node.

1.4.1 / 2021-08-18

  • Fix regression in v1.4.0 that did not pass comment nodes to the scrubber.

    Some scrubbers will want to override the default behavior and allow comments, but v1.4.0 only passed through elements to the scrubber's keep_node? method.

    This change once again allows the scrubber to make the decision on comment nodes, but still skips other non-elements like processing instructions (see #115).

    Mike Dalessio

1.4.0 / 2021-08-18

  • Processing Instructions are no longer allowed by Rails::Html::PermitScrubber

    Previously, a PI with a name (or "target") matching an allowed tag name was not scrubbed. There are no known security issues associated with these PIs, but similar to comments it's preferred to omit these nodes when possible from sanitized output.

    Fixes #115.

    Mike Dalessio

v1.3.0

  • Address deprecations in Loofah 2.3.0.

    Josh Goodall

v1.2.0

  • Remove needless white_list_sanitizer deprecation.

    By deprecating this, we were forcing Rails 5.2 to be updated or spew deprecations that users could do nothing about.

    That's pointless and I'm sorry for adding that!

    Now there's no deprecation warning and Rails 5.2 works out of the box, while Rails 6 can use the updated naming.

    Kasper Timm Hansen

... (truncated)

Changelog

Sourced from rails-html-sanitizer's changelog.

1.4.2 / 2021-08-23

  • Slightly improve performance.

    Assuming elements are more common than comments, make one less method call per node.

    Mike Dalessio

1.4.1 / 2021-08-18

  • Fix regression in v1.4.0 that did not pass comment nodes to the scrubber.

    Some scrubbers will want to override the default behavior and allow comments, but v1.4.0 only passed through elements to the scrubber's keep_node? method.

    This change once again allows the scrubber to make the decision on comment nodes, but still skips other non-elements like processing instructions (see #115).

    Mike Dalessio

1.4.0 / 2021-08-18

  • Processing Instructions are no longer allowed by Rails::Html::PermitScrubber

    Previously, a PI with a name (or "target") matching an allowed tag name was not scrubbed. There are no known security issues associated with these PIs, but similar to comments it's preferred to omit these nodes when possible from sanitized output.

    Fixes #115.

    Mike Dalessio

1.3.0

  • Address deprecations in Loofah 2.3.0.

    Josh Goodall

1.2.0

  • Remove needless white_list_sanitizer deprecation.

    By deprecating this, we were forcing Rails 5.2 to be updated or spew deprecations that users could do nothing about.

    That's pointless and I'm sorry for adding that!

    Now there's no deprecation warning and Rails 5.2 works out of the box, while Rails 6 can use the updated naming.

... (truncated)

Commits
  • c86fed1 version bump to v1.4.2
  • d494309 Merge pull request #118 from rails/flavorjones-tweak-comment-and-pi
  • b1fe437 perf: PermitScrubber#scrub checks node.element? before node.comment?
  • ab21d78 test: rewrite test coverage for comments and PIs
  • db9ccec ci: update default git branch
  • 97099c0 Merge pull request #119 from rails/flavorjones-port-ci-to-github-actions
  • e73f3e9 ci: remove travis and update the CI badge
  • 8d3db92 ci: add github actions workflow
  • b41bc7a version bump to v1.4.1
  • 04daa64 Merge pull request #117 from rails/flavorjones-comment-handling2
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/chaibio/chaipcr/network/alerts).
dependabot[bot] commented 2 years ago

Superseded by #77.