[PR #108] [MERGED] Bump activerecord from 7.0.3 to 7.0.3.1 #116

New Issue

adam · 2025-12-29T00:22:44+01:00

adam commented

2025-12-29 00:22:44 +01:00

📋 Pull Request Information

Original PR: https://github.com/plashchynski/crono/pull/108
Author: @dependabot[bot]
Created: 7/12/2022
Status: ✅ Merged
Merged: 7/24/2022
Merged by: @plashchynski

Base: main ← Head: dependabot/bundler/activerecord-7.0.3.1

📝 Commits (1)

811ab31 Bump activerecord from 7.0.3 to 7.0.3.1

📊 Changes

1 file changed (+60 additions, -60 deletions)

View changed files

📝 Gemfile.lock (+60 -60)

📄 Description

Bumps activerecord from 7.0.3 to 7.0.3.1.

Changelog

Sourced from activerecord's changelog.

Rails 7.0.3.1 (July 12, 2022)
Change ActiveRecord::Coders::YAMLColumn default to safe_load

This adds two new configuration options The configuration options are as follows:

config.active_storage.use_yaml_unsafe_load

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 not recommended, but can aid in upgrading.

config.active_record.yaml_column_permitted_classes

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:
config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time]
[CVE-2022-32224]

Commits

04972d9 Preparing for 7.0.3.1 release
0c68c1f updating version and changelog
9529dc8 Change ActiveRecord::Coders::YAMLColumn default to safe_load
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 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.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/plashchynski/crono/pull/108 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 7/12/2022 **Status:** ✅ Merged **Merged:** 7/24/2022 **Merged by:** [@plashchynski](https://github.com/plashchynski) **Base:** `main` ← **Head:** `dependabot/bundler/activerecord-7.0.3.1` --- ### 📝 Commits (1) - [`811ab31`](https://github.com/plashchynski/crono/commit/811ab3197849ee96464c410192378974a3c296f2) Bump activerecord from 7.0.3 to 7.0.3.1 ### 📊 Changes **1 file changed** (+60 additions, -60 deletions) <details> <summary>View changed files</summary> 📝 `Gemfile.lock` (+60 -60) </details> ### 📄 Description Bumps [activerecord](https://github.com/rails/rails) from 7.0.3 to 7.0.3.1. <details> <summary>Changelog</summary> Sourced from <a href="https://github.com/rails/rails/blob/v7.0.3.1/activerecord/CHANGELOG.md">activerecord's changelog</a>. <blockquote> <h2>Rails 7.0.3.1 (July 12, 2022)</h2> <ul> <li> Change ActiveRecord::Coders::YAMLColumn default to safe_load This adds two new configuration options The configuration options are as follows: <ul> <li><code>config.active_storage.use_yaml_unsafe_load</code></li> </ul> 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 not recommended, but can aid in upgrading. <ul> <li><code>config.active_record.yaml_column_permitted_classes</code></li> </ul> 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: <pre><code>config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time] </code></pre> [CVE-2022-32224] </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rails/rails/commit/04972d9b9ef60796dc8f0917817b5392d61fcf09"><code>04972d9</code></a> Preparing for 7.0.3.1 release</li> <li><a href="https://github.com/rails/rails/commit/0c68c1f71a3ab6fbd4a9878746fa94ddfe07a0f7"><code>0c68c1f</code></a> updating version and changelog</li> <li><a href="https://github.com/rails/rails/commit/9529dc844e001c03931e3579a03b89713d9c236f"><code>9529dc8</code></a> Change ActiveRecord::Coders::YAMLColumn default to safe_load</li> <li>See full diff in <a href="https://github.com/rails/rails/compare/v7.0.3...v7.0.3.1">compare view</a></li> </ul> </details> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=activerecord&package-manager=bundler&previous-version=7.0.3&new-version=7.0.3.1)](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> 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/plashchynski/crono/network/alerts). </details> --- 🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

adam added the pull-request label 2025-12-29 00:22:44 +01:00

adam closed this issue

2025-12-29 00:22:44 +01:00

adam referenced this issue

2025-12-29 00:22:47 +01:00

[PR #116] Bump activesupport from 7.0.3.1 to 7.0.4.1 #121

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/crono#116