-
Notifications
You must be signed in to change notification settings - Fork 33
chore: remove dotnet6 from docs and add migration guides for v2 and v3 #1021
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #1021 +/- ##
===========================================
- Coverage 78.13% 78.12% -0.01%
===========================================
Files 298 298
Lines 12003 12003
Branches 1441 1441
===========================================
- Hits 9378 9377 -1
Misses 2163 2163
- Partials 462 463 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
#### Extra keys - Breaking change | ||
If you're upgrading to v3, please review the [Migration Guide v3](../migration-guide-v3.md) for important breaking changes including .NET 8 requirement and AWS SDK v4 migration. | ||
|
||
In v1.x, the extra keys were added to the log entry as a dictionary. In v2.x, the extra keys are added to the log entry as |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved to dedicated page migration-guide-v2
|
||
!!! info | ||
|
||
Loooking for v1 specific documentation please go to [Metrics v1](/lambda/dotnet/core/metrics-v1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
moved to dedicated guide
|
Issue number: #1009
Summary
Changes
User experience
Checklist
Please leave checklist items unchecked if they do not apply to your change.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.