Skip to content

CHANGELOG.md

Latest commit

 

History

History
98 lines (60 loc) · 3.71 KB

CHANGELOG.md

File metadata and controls

98 lines (60 loc) · 3.71 KB

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

Changed

[0.1.12] - 2026-01-30

Added

  • Security: Default regex filter matchers for sensitive keys (password, token, secret, auth, cred, api_key, etc.)
  • Security: Job argument filtering for GoodJob/ActiveJob - respects log_arguments? class method
  • Security: SQL bind parameter filtering now detects JWT tokens and Bearer tokens

Fixed

  • Security: Reserved keys (src, evt, lvl, ts) in additional_data are now protected from being overwritten
  • CI: Fixed Ruby 4.0 bundler security error on GitHub Actions (world-writable gem directory)

[0.1.11] - 2026-01-28

Changed

  • Dev: Added jscpd task/config and refactored repeated helpers in tests and codegen

Fixed

  • Fix: Restore request logs in Puma cluster mode by reopening SemanticLogger in forked workers
  • Fix: Normalize ActiveJob and GoodJob timestamps to real wall clock time
  • Fix: Tagged logging now emits msg instead of message for AMS-style logs

[0.1.10] - 2026-01-23

Added

  • Feature: request_id now appears on all logs during a request, not just the request log

[0.1.9] - 2026-01-23

Changed

  • Fix: ActiveJob integration handles Rails main event reporter subscribers
  • Fix: Rack error handler avoids deprecated CSRF exception class on Rails main
  • CI: Added Rails main daily integration run and updated Rails test matrix (7.1.6, 7.2.3, 8.0.4, 8.1.2)

[0.1.8] - 2026-01-22

  • Fix: Lograge custom options now appear in request logs
  • Fix: Request logs include request metadata fields (request_id, source_ip, user_agent, referer, host, content_type, accept)
  • Docs: Documented Lograge custom options and request metadata fields

[0.1.7] - 2025-12-06

  • Fix: Puma server detection now uses $PROGRAM_NAME instead of checking defined?(::Puma::Server) which was unreliable
  • Fix: Test isolation for server_mode state in configuration tests
  • CI: Updated to Ruby 3.4.7 and Rails 8.1.1

[0.1.6] - 2025-11-30

  • Rename PROVIDER_PUSH_TOKEN secret to TF_PROVIDER_GITHUB_TOKEN

[0.1.5] - 2025-11-30

  • Fix: Development logs no longer wrapped in {message: "..."} when LogStruct is disabled
    • The TaggedLogging formatter monkey patch now checks LogStruct.enabled? before modifying log messages
    • This preserves original Rails logging behavior in development mode

[0.1.4] - 2025-10-13

  • Improve rack spoof handling and split integration setup

[0.1.3] - 2025-10-11

  • Fix: Changed storage, queue name, and format fields from String to Symbol type to match Rails conventions
    • Affected log types: ActiveStorage, CarrierWave, Shrine (storage field), ActiveJob, GoodJob (queue_name field), Request (format field)
  • JSON logging now enabled for all test runs (both local and CI) to ensure tests catch production bugs
    • Previously only enabled for CI test runs, now always enabled in test environment
    • This ensures local tests match CI behavior and catch serialization issues early
  • Fixed host authorization app

[0.1.2] - 2025-10-03

Better default policy for when JSON logs are enabled: machines get JSON, humans get readable logs. Enable LogStruct for production servers and test runs (both local and CI) to ensure tests catch production bugs. Keep dev-friendly logging on local machines or when running interactive commands on production servers.

[0.1.1] - 2025-09-29

Added dotenv-rails integration. Many other fixes and improvements.

[0.1.0] - 2025-09-07

Initial beta release.