Skip to content

chore(deps): update semantic_logger requirement from ~> 4.15 to >= 4.15, < 6.0 - #6

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/bundler/semantic_logger-gte-4.15-and-lt-6.0
Open

chore(deps): update semantic_logger requirement from ~> 4.15 to >= 4.15, < 6.0#6
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/bundler/semantic_logger-gte-4.15-and-lt-6.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 25, 2026

Copy link
Copy Markdown
Contributor

Updates the requirements on semantic_logger to permit the latest version.

Changelog

Sourced from semantic_logger's changelog.

[5.1.0] 2026-07-20

Deprecated

These are deprecated now and will be removed in v6. Each emits a Ruby deprecation warning (category: :deprecated), so it is silent by default and shown when deprecation warnings are enabled (for example ruby -W:deprecated, or Rails development mode).

  • The :sentry appender (SemanticLogger::Appender::Sentry), which depends on the end-of-life sentry-raven gem. Use the :sentry_ruby appender instead.
  • The :new_relic appender (SemanticLogger::Appender::NewRelic), which reports errors via newrelic_rpm. Use the log-forwarding :new_relic_logs appender instead.
  • The type: parameter on the Elasticsearch and OpenSearch appenders (:elasticsearch, :elasticsearch_http, and :opensearch). Document _type has been unused since Elasticsearch 7, so the parameter is now ignored on all server versions: the bulk appenders no longer send a _type, and the HTTP appender now posts to _doc.

Fixed

  • The file appender opens its log file when it is created, so a misconfigured path or insufficient permissions now raise immediately from SemanticLogger.add_appender, instead of surfacing later on the appender thread via the internal logger while log messages are lost. This restores the pre-4.9 behavior and matches the other appenders, which already open their resources eagerly. As a result the log file is created as soon as the appender is added, even if nothing is logged (the same as the standard Ruby and Rails loggers).

[5.0.0] 2026-06-29

Breaking changes

See the v5.0 upgrading guide for migration details.

  • Ruby 3.2 is now the minimum supported runtime. Earlier versions are end-of-life and are no longer tested.
  • Consolidate the asynchronous appender proxies: the worker thread and queue now live in an internal SemanticLogger::QueueProcessor, and SemanticLogger::Appender::AsyncBatch has been removed. batch: true now returns a SemanticLogger::Appender::Async (with #batch? true).
  • Appenders are now reopened automatically in the child process after fork (and Process.daemon). A Process._fork hook calls SemanticLogger.reopen for you, so most applications no longer need an after_fork/after_worker_boot hook. Disable with SemanticLogger.reopen_on_fork = false. Resolves #338.
  • Rename SemanticLogger::Formatters::Base#cleanse to #escape_control_characters. Custom formatters or subclasses that called the old method name must be updated.
  • Syslog records now escape control characters by default to prevent log injection. Resolves #190.

New features

  • Add opt-in logger caching: SemanticLogger.cache_loggers = true makes SemanticLogger[Class] (and the Loggable mixin) return a single shared Logger instance per class, so a later

... (truncated)

Commits
  • ee41292 Merge pull request #381 from reidmorrison/tech-debt/rubocop-todo-burndown
  • 3a02e17 Burn down rubocop_todo: set Layout/LineLength to 120, clear four cops
  • 13487bd Merge pull request #380 from reidmorrison/tech-debt/legacy-appender-deprecations
  • 70bcbfe docs: add v5.1 upgrade notes for switching off deprecated appenders
  • 02a2f19 Deprecate legacy service appenders and remove ES type; consolidate async ba...
  • cee1b11 Release 5.1.0
  • 725262e Merge pull request #379 from reidmorrison/fix/file-appender-eager-open
  • 213a697 docs: point the gem's changelog_uri at CHANGELOG.md
  • b2f0ba4 fix: open the file appender's log file eagerly at creation
  • cd3e84a Merge pull request #378 from reidmorrison/docs/accuracy-review
  • Additional commits viewable 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 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)

…15, < 6.0

Updates the requirements on [semantic_logger](https://github.com/reidmorrison/semantic_logger) to permit the latest version.
- [Changelog](https://github.com/reidmorrison/semantic_logger/blob/main/CHANGELOG.md)
- [Commits](reidmorrison/semantic_logger@v4.15.0...v5.1.0)

---
updated-dependencies:
- dependency-name: semantic_logger
  dependency-version: 5.1.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file ruby Pull requests that update ruby code labels Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file ruby Pull requests that update ruby code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants