Skip to content

chore(deps): update dependency apple/swift-log to from: "1.12.1"#106

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/apple-swift-log-1.x
Open

chore(deps): update dependency apple/swift-log to from: "1.12.1"#106
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/apple-swift-log-1.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 13, 2026

This PR contains the following updates:

Package Update Change
apple/swift-log minor from: "1.0.0"from: "1.12.1"

Release Notes

apple/swift-log (apple/swift-log)

v1.12.1

Compare Source

What's Changed

SemVer Patch
Other Changes

New Contributors

Full Changelog: apple/swift-log@1.12.0...1.12.1

v1.12.0

Compare Source

What's Changed

SemVer Minor
Other Changes

Full Changelog: apple/swift-log@1.11.0...1.12.0

v1.11.0

Compare Source

What's Changed

SemVer Minor
SemVer Patch
Other Changes

New Contributors

Full Changelog: apple/swift-log@1.10.1...1.11.0

v1.10.1

Compare Source

What's Changed

SemVer Minor

Full Changelog: apple/swift-log@1.10.0...1.10.1

v1.10.0

Compare Source

What's Changed

SemVer Minor
SemVer Patch
Other Changes

New Contributors

Full Changelog: apple/swift-log@1.9.1...1.10.0

v1.9.1

Compare Source

What's Changed

SemVer Patch
Other Changes
  • Change document title to 'SLG-0001: Metadata Providers' by @​ktoso in #​400

New Contributors

Full Changelog: apple/swift-log@1.9.0...1.9.1

v1.9.0

Compare Source

What's Changed

SemVer Minor
Other Changes

New Contributors

Full Changelog: apple/swift-log@1.8.0...1.9.0

v1.8.0

Compare Source

What's Changed

SemVer Minor
  • Conform Logger.Level to CustomStringConvertible and LosslessStringConvertible by @​fpseverino in #​395
Other Changes

New Contributors

Full Changelog: apple/swift-log@1.7.1...1.8.0

v1.7.1

Compare Source

What's Changed

SemVer Patch
Other Changes

Full Changelog: apple/swift-log@1.7.0...1.7.1

v1.7.0

Compare Source

What's Changed

SemVer Minor
SemVer Patch
Other Changes

New Contributors

Full Changelog: apple/swift-log@1.6.4...1.7.0

v1.6.4

Compare Source

What's Changed

SemVer Patch
Other Changes

New Contributors

Full Changelog: apple/swift-log@1.6.3...1.6.4

v1.6.3

Compare Source

What's Changed

SemVer Patch
Other Changes

New Contributors

Full Changelog: apple/swift-log@1.6.2...1.6.3

v1.6.2

Compare Source

What's Changed

SemVer Patch
Other Changes

New Contributors

Full Changelog: apple/swift-log@1.6.1...1.6.2

v1.6.1: Swift Log 1.6.1

Compare Source

SemVer Patch
  • Disable existential any build setting (#​312)

v1.6.0

Compare Source

SemVer Minor

  • Add Sendability annotations in #​308
  • Fix deprecation warnings around default log implementations on handlers in #​310
  • Drop Swift versions earlier than 5.8 in #​299
  • Implement Copy-On-Write (CoW) behavior for Logger struct by @​ayushi2103 in #​297
SemVer Patch
  • Replace standardOutput to standardError by @​ayushi2103 in #​295
  • Use Set to spot duplicated log handler warnings in #​306
  • Make protocol usage obvious using any and some keywords in #​307
  • Remove documentation for non-existent arguments by @​b1ackturtle in #​309
  • Remove Docc plugin which is no longer required in #​311
Other Changes

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

  • Avoid logging warnings when handler does not support metadataproviders by @​ktoso in #​252
  • Handle providers properly in multiplex log handler by @​ktoso in #​254
  • Add CI for Swift 5.8 and update nightly to Ubuntu 22.04 by @​yim-lee in #​255

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:

import Logging

enum Namespace { 
  @​TaskLocal static var simpleTraceID: String?
}

let simpleTraceIDMetadataProvider = Logger.MetadataProvider { 
    guard let traceID = Namespace.simpleTraceID else {
        return [:]
    }
    return ["simple-trace-id": .string(traceID)]
 }

LoggingSystem.bootstrap({ label, metadataProvider in
    myCoolLogHandler(label: label, metadataProvider: metadataProvider)
}, metadataProvider: simpleTraceIDMetadataProvider)

which in turn makes every Logger on this LoggingSystem add this contextual metadata to log statements automatically:

let log = Logger(label: "hello")

Namespace.$simpleTraceID.withValue("1234-5678") {
  test()
}

func test() {
  log.info("test log statement")
}

// [info] [simple-trace-id: 1234-5678] test log statement
Adoption in LogHandlers

In order to support this new feature in your log handlers, please make it accept a MetadataProvider? at creation, and store it as:

struct MyHandler: LogHandler {
    // ... 
    public var metadataProvider: Logger.MetadataProvider?
    // ...
}

What's Changed

Highlight
  • Metadata Providers (e.g. for Distributed Tracing) in LogHandlers by @​ktoso in #​238
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 that 5.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

  • [sendable] Sendable conformance checks cause errors on 5.6 but warnings on 5.7 by @​ktoso in #​229

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: #​218

What's Changed

New 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-less Logger.trace function.

For more details refer to #​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.

v1.4.0: SwiftLog 1.4.0

Compare Source

Highlights

This release addresses a missing public init in the newly introduced NoOpLogHandler. Please use 1.4.0 rather than 1.3.0 to be able to actually instantiate the that handler.

SemVer Minor
  • Add public init to NoOpLogHandler introduced in 1.3.0 #​142
Credits

This release contains a single PR: #​146

The complete change-list is available on the 1.4.0 milestone.

Thank you @​adam-fowler for spotting and fixing the mistake!

v1.3.0: SwiftLog 1.3.0

Compare Source

Highlights

LogHandler implementations should take care adjust their implementations moving forward to implement the following log function:

func log(
    level: Logging.Logger.Level, 
    message: Logging.Logger.Message, 
    metadata: Logging.Logger.Metadata?, 
    source: String, // new (!)
    file: String, function: String, line: UInt
)

rather than the previous function:

func log(
    level: Logging.Logger.Level, 
    message: Logging.Logger.Message, 
    metadata: Logging.Logger.Metadata?, 
    file: String, function: String, line: UInt
)

Compatibility shims are provided and existing implementations will continue to work as-is. However in order to reap benefits of the new source (which will contain the "module name from which this log message originates") parameter, they will have to change which log overload they implement. We suggest moving to implementing the new overload (with source:) as soon as possible, allowing the logging ecosystem to make use of this new capability.

For details see:

  • Add "source" for log messages #​135
SemVer Minor
  • Add "source" for log messages #​135
  • Add NoOpLogHandler for when you don't want logging #​142
  • Logging: port to Windows #​118
  • =multiplex #​139 more properly handle logLevel in multiplex handler #​140
    • Note that previous behavior of the MultiplexLogHandler was very surprising and this change makes it more consistent, see the PR for details if you are using multiplex handlers
SemVer Patch
  • silence #file to #filePath warnings #​133
  • a number of readme and docs improvements:
    • docs: =doc #​82 avoid showcasing internal lock in public docs #​144
    • Fix doc typo #​134
    • Add more syntax highlighting to the readme file #​114
  • and more, see the 1.3.0 milestone for all closed issues.
Credits

This release includes 15 issues/PRs, which were made possible with the help of 18 contributors 🎉

We would like to thank all everyone for their feedback and contributions:

Tomer Doron, Johannes Weiss, Konrad ktoso Malawski, Saleem Abdulrasool, Gwynne Raskind, prafsoni, Adam Fowler, Neal Lester, Artur Dryomov, Franz Busch, Shiva Huang, zach wick, Ravi Kandhadai, YR Chen, Jeremy Greenwood, Will Lisac, Mattt, Tanner

Thank you!

v1.2.0: SwiftLog 1.2.0

Compare Source

SemVer Major

  • Make log levels codable (#​99)

SemVer Minor

v1.1.1: SwiftLog 1.1.1

Compare Source

SemVer Patch
  • add flush api to default stdout/stderr logger (#​87)
  • Fix typo in LogHandler doc comment (#​76)
  • Link to ianpartridge/swift-log-syslog backend impl (#​73)
  • Fix documented ordering of Level (#​78)
  • Add Adorkable/swift-log-format-and-pipe to Backend list (#​83)
  • test formatting issues as part of sanity check (#​84)
  • better documentation around MetadataValue being expressible by literal
  • Add HeliumLogger to README (#​88)

v1.1.0: SwiftLog 1.1.0

Compare Source

SemVer Minor

  • Expose an API for configuring basic stdio log handling (#​61)
  • Added CaseIterable to Logger.Level enum (#​46)

SemVer Patch

  • Add internal section link to README.md (#​71)
  • add a CocoaPods podspec generator (#​54)
  • Update README.md
  • explain the upcoming SwiftLog 0 (#​69)
  • changed to isEmpty. (#​65)
  • docs: improve API documentation coverage (#​67)
  • Fix API documentation (#​66)
  • Add 'Show on GitHub' link to API docs (#​64)
  • add git commit template (#​62)
  • fix docs #file -> #function (#​59)
  • Fixed typo. (#​58)
  • add contribution guidelines and github default config (#​55)
  • fix linux tests formatting (#​45)
  • fix docker setup to use release version of swift 5 (#​48)
  • Link to more appropriate (still open) Swift issue (#​50)
  • Fix typo in "critical" words in docs (#​49)
  • retain SwiftNIO copyright header (#​44)
  • readme: fix log levels (#​43)
  • fix typo in API docs (#​42)
  • use consistent, swifty naming convention (#​41)

Configuration

📅 Schedule: (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 is behind base branch, 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.

@renovate renovate Bot changed the title chore(deps): update dependency apple/swift-log to from: "1.9.1" chore(deps): update dependency apple/swift-log to from: "1.10.1" Feb 16, 2026
@renovate renovate Bot force-pushed the renovate/apple-swift-log-1.x branch from 452d113 to 57fffbd Compare February 16, 2026 20:26
Copy link
Copy Markdown
Contributor

@dd-oleksii dd-oleksii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems counter-productive as it bumps the minimum required version, reducing the compatibility range for the application author.

@renovate renovate Bot force-pushed the renovate/apple-swift-log-1.x branch from 57fffbd to 6e6ba24 Compare March 24, 2026 07:50
@renovate renovate Bot force-pushed the renovate/apple-swift-log-1.x branch from 6e6ba24 to 0d223a2 Compare March 31, 2026 12:34
@renovate renovate Bot changed the title chore(deps): update dependency apple/swift-log to from: "1.10.1" chore(deps): update dependency apple/swift-log to from: "1.11.0" Mar 31, 2026
@renovate renovate Bot force-pushed the renovate/apple-swift-log-1.x branch 2 times, most recently from 83291b4 to c4086dd Compare April 14, 2026 16:21
@renovate renovate Bot changed the title chore(deps): update dependency apple/swift-log to from: "1.11.0" chore(deps): update dependency apple/swift-log to from: "1.12.0" Apr 14, 2026
@renovate renovate Bot force-pushed the renovate/apple-swift-log-1.x branch from c4086dd to 96602e7 Compare April 21, 2026 04:17
@renovate renovate Bot changed the title chore(deps): update dependency apple/swift-log to from: "1.12.0" chore(deps): update dependency apple/swift-log to from: "1.12.1" May 21, 2026
@renovate renovate Bot force-pushed the renovate/apple-swift-log-1.x branch from 96602e7 to 9637348 Compare May 21, 2026 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant