-
Notifications
You must be signed in to change notification settings - Fork 249
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
Deprecate the deprecator #494
Conversation
* update actions and gitlab CI * update project path * use trigger API to build internal docker instead * test trigger on branch push * fix github action * test why trigger workflow not starting * fix branch name * remove step in trigger job * remove test branch * move mirror to a separate workflow, update pipeline running rules * Revert "move mirror to a separate workflow, update pipeline running rules" This reverts commit 92b4b04. --------- Co-authored-by: Matic Lubej <[email protected]>
* remove "undefined" catch-all flag from a field * mypy fixes
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #494 +/- ##
=======================================
Coverage 91.95% 91.95%
=======================================
Files 55 55
Lines 4800 4800
=======================================
Hits 4414 4414
Misses 386 386
☔ View full report in Codecov by Sentry. |
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.
You plan to do a separate MR for preparing the release, right?
yes |
The deprecator from typing_extensions has additional benefits of IDEs picking it up
I wanted to deprecate our own deprecators, but then users would get spammed with stuff that they have no control over (since it would happen on import. So I want to wait with that (or just remove them after a while)