chore(deps): update dependency apple/swift-log to from: "1.5.4" - autoclosed #825
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
from: "1.4.0"
->from: "1.5.4"
Release Notes
apple/swift-log (apple/swift-log)
v1.5.4
Compare Source
What's Changed
Cleanups & minor compatibility improvements
Non code changes
New Contributors
Full Changelog: apple/swift-log@1.5.3...1.5.4
v1.5.3
Compare Source
What's Changed
Cleanups & minor compatibility improvements
Non code changes
New Contributors
Full Changelog: apple/swift-log@1.5.2...1.5.3
v1.5.2
Compare Source
Primary change
Address too aggressive warning logging on LogHandlers that do not support
MetadataProvider
. The warning would be emitted too frequently, resulting in flooding logs with warnings. Instead, the warning is now emitted once per log handler type.What's Changed
Full Changelog: apple/swift-log@1.5.1...1.5.2
v1.5.1
Compare Source
Summary
This patch release focuses on minor cleanups to ergonomics of setting metadata providers with the default stream log handlers, and fixes a bug in the default handler not printing the provided extra metadata by default (it does now).
Thank you to @slashmo for quickly noticing and providing a patch for the latter!
What's Changed
Full Changelog: apple/swift-log@1.5.0...1.5.1
v1.5.0
Compare Source
Changes
Swift version support
This release drops support for Swift 5.0.
Swift 5.1+ remain supported for the time being.
Logger.MetadataProvider
This release introduces metadata providers!
They are an additional way to add metadata to your log statements automatically whenever a log statement is about to be made. This works extremely well with systems like distributed tracing, that may pick up trace identifiers and other information from the task-local context from where the log statement is being made.
The feature came with a swift evolution style proposal introduction to the "why?" and "how?" of this feature you may find interesting.
Metadata providers are used like this:
which in turn makes every
Logger
on thisLoggingSystem
add this contextual metadata to log statements automatically:Adoption in
LogHandler
sIn order to support this new feature in your log handlers, please make it accept a
MetadataProvider?
at creation, and store it as:What's Changed
Highlight
Other changes
New Contributors
Full Changelog: apple/swift-log@1.4.4...1.5.0
v1.4.4
Compare Source
Sendable fixup for 1.4.3
The 1.4.3 release carefully introduced
Sendable
across the library; sadly we missed that5.6.x
Swift series treat a "missing marker protocol conformance for Sendable" as an error while it is intended to be a warning as which it is correctly reported in Swift 5.7.This release fixes this by not requiring that values stored in
Logger.MetadataValue.stringConvertible
must be Sendable, however practically speaking they should be thread-safe in any case, as it is not guaranteed in any way when/where this string convertible value will be invoked from.This release contains no other changes from 1.4.3.
What's Changed
Full Changelog: apple/swift-log@1.4.3...1.4.4
v1.4.3
Compare Source
Highlights
Loggers and all related types are now
Sendable
, including metadata values which have to be Sendable as well.When using from Swift that is concurrency aware, you may be getting warnings where you didn't before, these are all correct though - you need to be ready for e.g. logger metadata to be accessed from another thread. Thankfully values logged this way should usually be sendable to begin with, preferably value types.
For more details see: https://github.com/apple/swift-log/pull/218
What's Changed
SwiftLogNoOpLogHandler.init(_: String)
by @glbrntt in https://github.com/apple/swift-log/pull/194New Contributors
Full Changelog: apple/swift-log@1.4.2...1.4.3
v1.4.2
Compare Source
This release fixes a single bug in the propagation of the
function
parameter in the source-lessLogger.trace
function.For more details refer to https://github.com/apple/swift-log/pull/185 - thank you noticing and fixing the issue @saulbaro!
You can find additional details on all changes in this release in the 1.4.2 milestone.
v1.4.1
Compare Source
This patch release fixes some compatibility issues, including a Windows compatibility issue as well as wrongly removed APIs in the 1.3.0->1.4.0 transition.
No new features were added in this release.
You can refer to the detailed changes by inspecting the issues linked form the 1.4.1 milestone.
Configuration
📅 Schedule: 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.
This PR has been generated by Mend Renovate. View repository job log here.