You are viewing a plain text version of this content. The canonical link for it is here.
Posted to distributedlog-issues@bookkeeper.apache.org by GitBox <gi...@apache.org> on 2023/01/20 11:51:59 UTC
[GitHub] [distributedlog] dependabot[bot] opened a new pull request, #259: Bump activesupport from 5.2.0 to 5.2.8.1 in /website
dependabot[bot] opened a new pull request, #259:
URL: https://github.com/apache/distributedlog/pull/259
Bumps [activesupport](https://github.com/rails/rails) from 5.2.0 to 5.2.8.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/rails/rails/releases">activesupport's releases</a>.</em></p>
<blockquote>
<h2>5.2.8.1</h2>
<h2>Active Support</h2>
<ul>
<li>No changes.</li>
</ul>
<h2>Active Model</h2>
<ul>
<li>No changes.</li>
</ul>
<h2>Active Record</h2>
<ul>
<li>
<p>Change ActiveRecord::Coders::YAMLColumn default to safe_load</p>
<p>This adds two new configuration options The configuration options are as
follows:</p>
<ul>
<li><code>config.active_storage.use_yaml_unsafe_load</code></li>
</ul>
<p>When set to true, this configuration option tells Rails to use the old
"unsafe" YAML loading strategy, maintaining the existing behavior but leaving
the possible escalation vulnerability in place. Setting this option to true
is <em>not</em> recommended, but can aid in upgrading.</p>
<ul>
<li><code>config.active_record.yaml_column_permitted_classes</code></li>
</ul>
<p>The "safe YAML" loading method does not allow all classes to be deserialized
by default. This option allows you to specify classes deemed "safe" in your
application. For example, if your application uses Symbol and Time in
serialized data, you can add Symbol and Time to the allowed list as follows:</p>
<pre><code>config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time]
</code></pre>
<p>[CVE-2022-32224]</p>
</li>
</ul>
<h2>Action View</h2>
<ul>
<li>No changes.</li>
</ul>
<h2>Action Pack</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/rails/rails/commit/8030cff808657faa44828de001cd3b80364597de"><code>8030cff</code></a> Preparing for 5.2.8.1 release</li>
<li><a href="https://github.com/rails/rails/commit/ec10235df6c5f502e9551573367f87be48b1259c"><code>ec10235</code></a> updating version and changelog</li>
<li><a href="https://github.com/rails/rails/commit/26521331e5923a0c50fa50984d2f924e5f26c50b"><code>2652133</code></a> Preparing for 5.2.8 release</li>
<li><a href="https://github.com/rails/rails/commit/a1b8a9b5e5a905d0aeabf532e3f6b74116d5cce6"><code>a1b8a9b</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/rails/rails/issues/45027">#45027</a> from rails/fix-tag-helper-regression</li>
<li><a href="https://github.com/rails/rails/commit/9f3761a43ea92da8ae4ed828656153f40d337e81"><code>9f3761a</code></a> Merge branch '5-2-sec' into 5-2-stable</li>
<li><a href="https://github.com/rails/rails/commit/b290430faf946b298352196e245f227f762f8c08"><code>b290430</code></a> Preparing for 5.2.7.1 release</li>
<li><a href="https://github.com/rails/rails/commit/2d8cb453d69ea3d31d04e22474d523412cd92566"><code>2d8cb45</code></a> Update changelogs for release</li>
<li><a href="https://github.com/rails/rails/commit/1278c0f0b4a18ea199f92b666b8b94954a74c20b"><code>1278c0f</code></a> Fix and add protections for XSS in names.</li>
<li><a href="https://github.com/rails/rails/commit/de20f93f4e800b4820341b05dab23fe01f879fdf"><code>de20f93</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/rails/rails/issues/38069">#38069</a> from y-yagi/make_load_interlock_aware_monitor_work_...</li>
<li><a href="https://github.com/rails/rails/commit/459e7cf62252558bbf65f582a230562ab1a76c5e"><code>459e7cf</code></a> Preparing for 5.2.7 release</li>
<li>Additional commits viewable in <a href="https://github.com/rails/rails/compare/v5.2.0...v5.2.8.1">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
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/apache/distributedlog/network/alerts).
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: distributedlog-issues-unsubscribe@bookkeeper.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org