Skip to content

Conversation

@TerryHowe
Copy link
Member

No description provided.

@codecov
Copy link

codecov bot commented Nov 24, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.54%. Comparing base (0324380) to head (65f66b5).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1057   +/-   ##
=======================================
  Coverage   82.54%   82.54%           
=======================================
  Files          64       64           
  Lines        4779     4779           
=======================================
  Hits         3945     3945           
- Misses        510      511    +1     
+ Partials      324      323    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@shizhMSFT shizhMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is too early for this doc. At least, we should have an v3 alpha version first.

@shizhMSFT shizhMSFT changed the title feat: add v3 migration doc docs: add v3 migration doc Dec 9, 2025
@TerryHowe
Copy link
Member Author

Well, if we have it, we can iterate on it rather than try to figure it out after the fact.

@TerryHowe TerryHowe force-pushed the feat-v3-migration-doc branch from 645f03b to 3660229 Compare December 21, 2025 12:52
@TerryHowe TerryHowe requested a review from sabre1041 as a code owner December 21, 2025 12:52
Copy link
Contributor

@sabre1041 sabre1041 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good start. While we are still in initial design/development mode, it would be good to note that the migration path is still under development explicitly in this document

Also, is this document to be linked/referenced from another document?

@TerryHowe TerryHowe force-pushed the feat-v3-migration-doc branch from 3660229 to 8055d9f Compare December 22, 2025 11:39
@TerryHowe
Copy link
Member Author

I updated the document to note it is a work in progress.

I was hoping to that each breaking change PR would make a note in this document.

When this release is done, it would be moved to the document site.

@TerryHowe TerryHowe force-pushed the feat-v3-migration-doc branch from 8055d9f to e0d5a05 Compare January 1, 2026 16:01
@TerryHowe
Copy link
Member Author

I've changed this so it creates a directory so we won't need to deal with merge conflicts. Each breaking change can have a short document and at the end we'll take them all add them to the docs site.

@TerryHowe TerryHowe force-pushed the feat-v3-migration-doc branch from e0d5a05 to 65f66b5 Compare January 1, 2026 16:02
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.

3 participants