You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[!WARNING]
This version was incorrectly released using a SHA pointing to a newer version for immutable actions only. Please use v3.4.2 (or v3) instead.
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).
If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0
If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
After 10 years, with many corner cases covered, very few issues pending (at least, comparing them with the usage of the library as part of Docker, Kubernetes, Datadog's agent, etc.), and a very stable API, I think it's time to release a 1.0.0 version.
This version will be released under a vanity URL: dario.cat/mergo
PS: although I'll make sure that github.com/imdario/mergo will be available, I'm going to also change my GitHub handle, so expect for a few minutes to not be able to pull from github.com/imdario as I fork it from the new handle to the old one.
PS2: I'm creating a discussion for this release to make sure we can have a conversation around the topic, and anything else about Mergo that you care about.
v0.3.15: Issues #131, #170, #220, and #202 fixed
This version, while only a patch bump, includes a (very minor) breaking change: the flag.ParseErrorsWhitelist struct and corresponding FlagSet.parseErrorsWhitelist field have been renamed to ParseErrorsAllowlist.
This should result in compilation errors in any code that uses these fields, which can be fixed by adjusting the names at call sites. There is no change in semantics or behavior of the struct or field referred to by these names. If your code compiles without errors after bumping to/past v1.0.8, you are not affected by this change.
The breaking change was reverted in v1.0.9, by means of re-introducing the old names with deprecation warnings. The plan is still to remove them in a future release, so if your code does depend on the old names, please change them to use the new names at your earliest convenience.
renovateBot
changed the title
chore(deps): update golang.org/x/crypto commit hash to 4be66e5
chore(deps): update golang.org/x/crypto commit hash to c1f2f97
Nov 17, 2020
renovateBot
changed the title
chore(deps): update golang.org/x/crypto commit hash to c1f2f97
chore(deps): update golang.org/x/crypto commit hash to c8d3bf9
Nov 24, 2020
Thank you for this automated update! This meta-PR from 2020 is now superseded by individual dependency PRs. Closing in favor of those more recent, targeted updates.
This file contains hidden or 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
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:
v3.2.6→v3.5.03.16.0→3.23.3v1.0.0→v1.0.1v0.3.12→v0.3.16v0.0.3→v0.0.6v1.7.2→v1.8.1v1.0.5→v1.0.10v1.8.1→v1.21.0v1.22.9→v1.22.17v1.21.0→v1.27.11.19.2-alpine→1.25.6-alpinev0.0.0-20201112155050-0c6587e931a9→v0.47.0v0.0.0-20210405180319-a5a99cb37ef4→v0.49.0v0.0.0-20200630173020-3af7569d3a1e→v0.14.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
actions/cache (actions/cache)
v3.5.0Compare Source
actions/cacheto v4.1.0Full Changelog: actions/cache@v3...v3.5.0
v3.4.3Compare Source
What's Changed
Full Changelog: actions/cache@v3.4.2...v3.4.3
v3.4.2Compare Source
What's Changed
Full Changelog: actions/cache@v3.4.0...v3.4.2
v3.4.1Compare Source
v3.4.0Compare Source
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version
v4orv3as soon as possible before February 1st, 2025. (Upgrade instructions below).If you are using pinned SHAs, please use the SHAs of versions
v4.2.0orv3.4.0If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
1.11.11.1.30.38.3Full Changelog: actions/cache@v3.3.3...v3.4.0
v3.3.3Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.3
v3.3.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.2
v3.3.1Compare Source
What's Changed
Full Changelog: actions/cache@v3...v3.3.1
v3.3.0Compare Source
What's Changed
lookup-onlyoption by @cdce8p in #1041New Contributors
Full Changelog: actions/cache@v3...v3.3.0
dustin/go-humanize (github.com/dustin/go-humanize)
v1.0.1Compare Source
imdario/mergo (github.com/imdario/mergo)
v0.3.16: Announcement: v1.0.0 will be released on June 18thCompare Source
This release doesn't contain code changes.
After 10 years, with many corner cases covered, very few issues pending (at least, comparing them with the usage of the library as part of Docker, Kubernetes, Datadog's agent, etc.), and a very stable API, I think it's time to release a 1.0.0 version.
This version will be released under a vanity URL: dario.cat/mergo
PS: although I'll make sure that github.com/imdario/mergo will be available, I'm going to also change my GitHub handle, so expect for a few minutes to not be able to pull from github.com/imdario as I fork it from the new handle to the old one.
PS2: I'm creating a discussion for this release to make sure we can have a conversation around the topic, and anything else about Mergo that you care about.
v0.3.15: Issues #131, #170, #220, and #202 fixedCompare Source
v0.3.14: fix: Respect overwriteWithEmptySrc when merging maps #231Compare Source
v0.3.13: Merging same-type slices supported, YAML upgraded to v3 (only used in tests), and more flexibility for transformersCompare Source
What's Changed
New Contributors
Full Changelog: darccio/mergo@0.3.12...v0.3.13
mattn/go-zglob (github.com/mattn/go-zglob)
v0.0.6Compare Source
v0.0.5Compare Source
v0.0.4Compare Source
smartystreets/goconvey (github.com/smartystreets/goconvey)
v1.8.1Compare Source
v1.8.0: - Updating to Go 1.18Compare Source
What's Changed
New Contributors
Full Changelog: smartystreets/goconvey@v1.7.2...v1.8.0
spf13/pflag (github.com/spf13/pflag)
v1.0.10Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.9...v1.0.10
v1.0.9Compare Source
What's Changed
Full Changelog: spf13/pflag@v1.0.8...v1.0.9
v1.0.8Compare Source
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhiteliststruct and correspondingFlagSet.parseErrorsWhitelistfield have been renamed toParseErrorsAllowlist.This should result in compilation errors in any code that uses these fields, which can be fixed by adjusting the names at call sites. There is no change in semantics or behavior of the struct or field referred to by these names. If your code compiles without errors after bumping to/past v1.0.8, you are not affected by this change.
The breaking change was reverted in v1.0.9, by means of re-introducing the old names with deprecation warnings. The plan is still to remove them in a future release, so if your code does depend on the old names, please change them to use the new names at your earliest convenience.
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.7...v1.0.8
v1.0.7Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.6...v1.0.7
v1.0.6Compare Source
What's Changed
pkg/flagcompatibility by @mckern in #220New Contributors
Full Changelog: spf13/pflag@v1.0.5...v1.0.6
spf13/viper (github.com/spf13/viper)
v1.21.0Compare Source
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
mapstructurepackage replacement. by @aldas in #2004New Contributors
Full Changelog: spf13/viper@v1.20.0...v1.21.0
v1.20.1Compare Source
What's Changed
Bug Fixes 🐛
Full Changelog: spf13/viper@v1.20.0...v1.20.1
v1.20.0Compare Source
What's Changed
Exciting New Features 🎉
Enhancements 🚀
Bug Fixes 🐛
Breaking Changes 🛠
Dependency Updates ⬆️
Other Changes
New Contributors
Full Changelog: spf13/viper@v1.19.0...v1.20.0
v1.19.0Compare Source
What's Changed
Bug Fixes 🐛
Dependency Updates ⬆️
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.
👻 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.