-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update all non-major dependencies #10
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor-patch
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
300f325
to
b801728
Compare
b801728
to
38cfb5d
Compare
38cfb5d
to
48db23d
Compare
48db23d
to
2ce4cc3
Compare
2ce4cc3
to
ad8e272
Compare
ee7f087
to
845bcd1
Compare
e82922b
to
b6ba756
Compare
b6ba756
to
8e6d0f6
Compare
8e6d0f6
to
5d7ed65
Compare
5d7ed65
to
de8791d
Compare
de8791d
to
7b9bd6d
Compare
0b82720
to
7544375
Compare
8849744
to
050c87a
Compare
050c87a
to
eba2fef
Compare
eba2fef
to
a3023bd
Compare
a3023bd
to
95bf77a
Compare
95bf77a
to
dd94166
Compare
86c782b
to
00d9fe5
Compare
00d9fe5
to
2c558d3
Compare
9b64838
to
3511909
Compare
3511909
to
a784bc3
Compare
a784bc3
to
ec8eadd
Compare
ec8eadd
to
aa1802b
Compare
aa1802b
to
2870177
Compare
a20449c
to
3f2588c
Compare
3f2588c
to
b40dc02
Compare
b40dc02
to
6eb4bb6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.2"
->from: "1.6.2"
from: "0.3.1"
->from: "0.4.0"
v3.1.0
->v3.4.6
Release Notes
apple/swift-log (apple/swift-log)
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.1Compare Source
SemVer Patch
v1.6.0
Compare Source
SemVer Minor
SemVer Patch
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
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
g-mark/SwiftPath (g-mark/SwiftPath)
v0.4.0
Compare Source
kubewarden/github-actions (kubewarden/github-actions)
v3.4.6
Compare Source
🐛 Bug Fixes
🧰 Maintenance
v3.4.5
Compare Source
🚀 Features
🐛 Bug Fixes
v3.4.4
Compare Source
🧰 Maintenance
v3.4.3
Compare Source
🐛 Bug Fixes
v3.4.2
Compare Source
🐛 Bug Fixes
v3.4.1
Compare Source
🐛 Bug Fixes
🧰 Maintenance
v3.4.0
Compare Source
🚀 Features
🧰 Maintenance
v3.3.5
Compare Source
v3.3.4
Compare Source
v3.3.3
Compare Source
🚀 Features
v3.3.2
Compare Source
🧰 Maintenance
v3.3.1
Compare Source
🐛 Bug Fixes
v3.3.0
Compare Source
🧰 Maintenance
v3.2.0
Compare Source
🧰 Maintenance
v3.1.20
Compare Source
🧰 Maintenance
v3.1.19
Compare Source
🚀 Features
🐛 Bug Fixes
🧰 Maintenance
v3.1.18
Compare Source
v3.1.17
Compare Source
v3.1.16
Compare Source
v3.1.15
Compare Source
v3.1.14
Compare Source
v3.1.13
Compare Source
v3.1.12
Compare Source
🧰 Maintenance
v3.1.11
Compare Source
v3.1.10
Compare Source
🧰 Maintenance
v3.1.9
Compare Source
🚀 Features
🐛 Bug Fixes
v3.1.8
Compare Source
v3.1.7
Compare Source
🚀 Features
🧰 Maintenance
v3.1.6
Compare Source
🧰 Maintenance
v3.1.5
Compare Source
v3.1.4
Compare Source
v3.1.3
Compare Source
v3.1.2
Compare Source
🐛 Bug Fixes
🧰 Maintenance
v3.1.1
Compare Source
🐛 Bug Fixes
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.