[dependabot]

Bumps the bundler group with 2 updates in the / directory: activesupport and rack.

Updates activesupport from 8.1.4 to 8.1.4.1

Release notes

Sourced from activesupport's releases.

8.1.4.1

Active Support

• ActiveSupport::MessagePack no longer deserializes an unsafe ActiveSupport::SafeBuffer as html_safe.

  A SafeBuffer that was no longer html_safe?, for example after an in-place gsub!, was deserialized as an html_safe SafeBuffer. It is now serialized with an unsafe marker and deserialized as a String. Earlier versions of Rails cannot read an unsafe buffer serialized this way.

  [GHSA-2w9f-fxwj-w2qf]

  Jean Boussier

• ActiveSupport::Inflector#safe_constantize matches the constant name in a LoadError message as a literal string instead of building a Regexp from it.

  The name's segments were interpolated unescaped into the pattern, so input that reaches safe_constantize, such as the channel identifier in an Action Cable subscribe command, chose the source passed to the regexp compiler.

  [GHSA-8474-xrp6-wh69]

  Jeremy Daer

Active Model

• No changes.

Active Record

• No changes.

Action View

• Skip attribute names in tag helpers that are blank once converted to a string.

  A Symbol such as :" " is not blank, because Symbol#blank? is Symbol#empty?, so it reached the escaping step and produced an attribute with no name. The asset helpers symbolize their keys, so an ordinary String key reached the same place.

  [GHSA-68p9-83h6-5wpj]

  Mike Dalessio

... (truncated)

Changelog

Sourced from activesupport's changelog.

Rails 8.1.4.1 (November 03, 2026)

• ActiveSupport::MessagePack no longer deserializes an unsafe ActiveSupport::SafeBuffer as html_safe.

  A SafeBuffer that was no longer html_safe?, for example after an in-place gsub!, was deserialized as an html_safe SafeBuffer. It is now serialized with an unsafe marker and deserialized as a String. Earlier versions of Rails cannot read an unsafe buffer serialized this way.

  [GHSA-2w9f-fxwj-w2qf]

  Jean Boussier

• ActiveSupport::Inflector#safe_constantize matches the constant name in a LoadError message as a literal string instead of building a Regexp from it.

  The name's segments were interpolated unescaped into the pattern, so input that reaches safe_constantize, such as the channel identifier in an Action Cable subscribe command, chose the source passed to the regexp compiler.

  [GHSA-8474-xrp6-wh69]

  Jeremy Daer

Commits

• 3f290b7 Preparing for 8.1.4.1 release
• 4ca0906 ActiveSupport::MessagePack preserve SafeBuffer html_safe status
• 95aa9e4 Avoid dynamic regexp in safe_constantize LoadError handling
• See full diff in compare view

Updates rack from 3.2.7 to 3.2.8

Changelog

Sourced from rack's changelog.

[3.2.8] - 2026-10-30

Security

• GHSA-5v64-555j-wjxm Multipart parser retains parsed data in its scan buffer, allowing denial of service via memory exhaustion.
• GHSA-wvg4-6p58-3gh3 Rack::Static header rules were matched against an unnormalized path, allowing dot segments to bypass them.
• GHSA-2j8w-xcrc-x985 Rack::Request#host_with_port, #base_url, and #url returned the raw authority when it was invalid; host_with_port now returns nil in that case.
• GHSA-p8x9-v4hv-2w4g Multipart requests with more than one boundary parameter were accepted when the first value was empty or began with a quote, semicolon, or comma, bypassing the guard added for CVE-2026-26961.

Fixed

• Rack::Multipart::UploadedFile now delegates keyword arguments to the wrapped tempfile. Calls such as uploaded_file.readlines(chomp: true) raised TypeError on Ruby 3.0+. (#2481, #2501, @​SeanLF)

Commits

• 5f511d7 Bump patch version.
• 3e01d71 Update changelog.
• a295123 Reject multipart content types with a boundary parameter before the parsed one.
• 49386f4 Don't leak invalid Host through host_with_port.
• 18a07fe Normalize static header rule paths before matching.
• 244e75a Remove parsed bytes from the multipart buffer while reading parts.
• 3519905 Backport UploadedFile keyword forwarding fix (#2501)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dependabot]

Looks like these dependencies are no longer updatable, so this is no longer needed.