[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@logtape/logtape (source)	^2.3.5 → ^2.3.6

---

Release Notes

dahlia/logtape (@​logtape/logtape)

v2.3.6

Compare Source

Released on September 19, 2026.

@​logtape/logtape

• Fixed logging a value which contains a circular reference throwing
  TypeError: Converting circular structure to JSON. Such a reference is
  now rendered as the string "[Circular]" wherever LogTape falls back to
  JSON serialization: in jsonLinesFormatter on every runtime, and in
  defaultTextFormatter, ansiColorFormatter, and logfmtFormatter on
  runtimes which provide neither Deno.inspect() nor Node.js'
  util.inspect(), such as browsers, React Native, and edge functions.
  A value which merely occurs more than once, as opposed to containing
  itself, is still serialized in full.
  [#​218, #​221]
• Fixed fingersCrossed() throwing
  TypeError: Converting circular structure to JSON when a context value
  selected by isolateByContext.keys contains a circular reference. Buffers
  are still isolated by the context values themselves, so two contexts which
  differ only in where their circular references point are not merged into
  one buffer.
  [#​220, #​222]

@​logtape/cloudwatch-logs

• Fixed the default formatter throwing
  TypeError: Converting circular structure to JSON when an interpolated
  message value contains a circular reference. Such a reference is now
  rendered as the string "[Circular]".
  [#​218, #​221]

@​logtape/fastify

• Fixed the Pino-compatible logger's %j, %o, and %O conversions
  throwing TypeError: Converting circular structure to JSON when the
  corresponding argument contains a circular reference. Such a reference is
  now rendered as the string "[Circular]".
  [#​218, #​221]

@​logtape/hono

• Fixed honoLogger() reporting the response time before the response body
  stream had completed, which made streamed responses (e.g. from
  streamText()) look much faster than they were. The middleware now logs
  when the body stream finishes, errors, or is cancelled, while preserving
  the implicit context that was active when the request finished. Because
  the response body is now wrapped, a streamed response is only logged if
  the body is consumed (as a real HTTP server does), and responses are sent
  as streams rather than with runtime-generated Content-Length framing.
  Responses with a null or already-locked body, and HEAD responses, are
  logged immediately as before.
  [#​219, #​223]

@​logtape/pretty

• Fixed the pretty formatter throwing
  TypeError: Converting circular structure to JSON when rendering a value
  which contains a circular reference on runtimes which provide neither
  Deno.inspect() nor Node.js' util.inspect(), such as browsers, React
  Native, and edge functions. Such a reference is now rendered as the string
  "[Circular]".
  [#​218, #​221]

@​logtape/sentry

• Fixed the Sentry sink throwing
  TypeError: Converting circular structure to JSON when rendering an
  interpolated message value which contains a circular reference on runtimes
  which provide neither Deno.inspect() nor Node.js' util.inspect(), such
  as browsers, React Native, and edge functions. The 2.2.1 fix for
  [#​180] covered only Deno, Node.js, and
  Bun.
  [#​218, #​221]

@​logtape/syslog

• Fixed message rendering throwing
  TypeError: Converting circular structure to JSON when an interpolated
  message value contains a circular reference. Such a reference is now
  rendered as the string "[Circular]".
  [#​218, #​221]

@​logtape/windows-eventlog

• Fixed the default formatter throwing
  TypeError: Converting circular structure to JSON when an interpolated
  message value or a property contains a circular reference. Such a
  reference is now rendered as the string "[Circular]".
  [#​218, #​221]

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: llm-ring/lmring/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: aa4d2b6e-e85b-4a8d-b9a3-d5979addd5e1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
lmring-web	Ready	Preview	Sep 19, 2026 5:43pm UTC

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!