Skip to content

Releases: envylabs/faraday-detailed_logger

v2.6.1

20 Apr 17:38
5a65ae9

Choose a tag to compare

2.6.1 (2025-04-20)

Bug Fixes

  • re-release of v2.6.0 after release automation corrections (0deca63)

v2.6.0

20 Apr 17:13
98df3c0

Choose a tag to compare

2.6.0 (2025-04-20)

Features

  • set minimum Ruby to version 3.2 (d6e5bd4)

v2.5.0

23 Jan 18:05

Choose a tag to compare

  • Add faraday 2 support.
  • Extract an initial internal cURL formatter

v2.4.1

09 Nov 15:33

Choose a tag to compare

chore: 2.4.1 release

v2.4.0

06 Nov 17:50

Choose a tag to compare

chore: 2.4.0 release

v2.3.0

11 Feb 19:02

Choose a tag to compare

2.3.0 release

v2.1.2

21 Aug 14:57

Choose a tag to compare

Changelog

  • Update the middleware to allow the logger and tags to be publicly accessible. This is not necessarily intended to be developer-used, but rather fix warnings in older versions of Ruby.

v2.1.1

21 Aug 14:56

Choose a tag to compare

Changelog

  • Require faraday ~> 0.8. This change only makes explicit the minimum version of faraday which is supported.

v2.1.0

12 Oct 20:30
bfbb320

Choose a tag to compare

Changelog

  • Catch StandardError exceptions to log and re-raise them.

v2.0.0

12 Oct 20:31

Choose a tag to compare

Changelog

  • Remove Logger progname support/configuration. Varying the progname appears
    to make logging in a syslog-like environment unnecessarily more difficult.
  • Add tagging support to the logger. Any number of tags may be given which will
    be prepended to all lines logged. This is largely follows the
    ActiveSupport::TaggedLogging log functionality. "Old" usages of this library
    will treat any previous progname strings as a tag and continue to record
    them to the log. Even though the progname is now logged as a tag, this is
    still considered a breaking change just in case system configurations were
    dependent on the progname for log output redirection (syslog).