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

Update dependency Microsoft.Extensions.Configuration to v9 #108

Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 21, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Microsoft.Extensions.Configuration (source) 8.0.0 -> 9.0.0 age adoption passing confidence

Release Notes

dotnet/runtime (Microsoft.Extensions.Configuration)

v9.0.0: .NET 9.0.0

Release

What's Changed

Full Changelog: dotnet/runtime@v9.0.0-rc.2.24473.5...v9.0.0


Configuration

📅 Schedule: Branch creation - "before 07:00 on Thursday" in timezone Europe/Oslo, 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@hggutvik
Copy link

hggutvik commented Nov 27, 2024

Closing all dotnet v9 PRs from renovate for now, as this major upgrade of .NET will be handled in a separate issue (#110 )

@hggutvik hggutvik closed this Nov 27, 2024
@hggutvik hggutvik deleted the renovate/microsoft.extensions.configuration-9.x branch November 27, 2024 09:25
Copy link
Contributor Author

renovate bot commented Nov 27, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 9.x releases. But if you manually upgrade to 9.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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