Skip to content
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

fix(deps): update module github.com/imdario/mergo to v0.3.16 #4798

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 22, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/imdario/mergo v0.3.15 -> v0.3.16 age adoption passing confidence

Release Notes

imdario/mergo (github.com/imdario/mergo)

v0.3.16: Announcement: v1.0.0 will be released on June 18th

Compare 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.


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 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 requested a review from a team as a code owner January 22, 2024 12:38
@renovate renovate bot force-pushed the renovate/git.luolix.top-imdario-mergo-0.x branch 5 times, most recently from 08676f0 to 9feb9b2 Compare January 29, 2024 05:47
@renovate renovate bot force-pushed the renovate/git.luolix.top-imdario-mergo-0.x branch 7 times, most recently from 69145bc to 57d6b99 Compare February 5, 2024 10:26
@renovate renovate bot force-pushed the renovate/git.luolix.top-imdario-mergo-0.x branch 5 times, most recently from 1361802 to c89c031 Compare February 12, 2024 07:58
@renovate renovate bot force-pushed the renovate/git.luolix.top-imdario-mergo-0.x branch 11 times, most recently from cf6434c to fd660b9 Compare February 26, 2024 12:09
@renovate renovate bot force-pushed the renovate/git.luolix.top-imdario-mergo-0.x branch from fd660b9 to dfe4dcf Compare February 28, 2024 15:07
@renovate renovate bot force-pushed the renovate/git.luolix.top-imdario-mergo-0.x branch 8 times, most recently from 18be36e to 7b23179 Compare August 20, 2024 08:53
@renovate renovate bot force-pushed the renovate/git.luolix.top-imdario-mergo-0.x branch 6 times, most recently from 232b4d1 to ae7fb3d Compare August 30, 2024 12:49
@renovate renovate bot force-pushed the renovate/git.luolix.top-imdario-mergo-0.x branch 7 times, most recently from 2c789b1 to a3f3a0c Compare September 12, 2024 07:18
@renovate renovate bot force-pushed the renovate/git.luolix.top-imdario-mergo-0.x branch 6 times, most recently from 00806ca to ee7c900 Compare September 16, 2024 10:35
@renovate renovate bot force-pushed the renovate/git.luolix.top-imdario-mergo-0.x branch from ee7c900 to 996374c Compare September 17, 2024 11:11
Copy link

sonarcloud bot commented Sep 17, 2024

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.

0 participants