Skip to content

First pass of deprecation removals for 0.103.0 #3993

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

zm711
Copy link
Member

@zm711 zm711 commented Jun 18, 2025

I just did a search of the code base for all our dep warnings for removals in 0.103.0 and removed, updated some docs related to the deps and fixed tests that I could find. I probably missed something so I'll keep it on draft for the moment.

@zm711 zm711 added the deprecations Related to code deprecation label Jun 18, 2025
@zm711
Copy link
Member Author

zm711 commented Jun 18, 2025

What I haven't changed 1) our the waveform extractor combability. It was listened as maybe remove for 0.103.0 but I say keep--maybe to discuss at a maintenance meeting
2) the new wait to do automerge. (Selfishly I'm using the old api :) )

@zm711
Copy link
Member Author

zm711 commented Jun 18, 2025

I would like to suggest as we update deprecations (myself included) that we try to add a comment in the tests as well with the deprecation version to make it easier to find. I tried searching based on deprecation term, but missed a few in testing as we can see from the failed testing. I think the extra effort will speed this along moving forward :)

@zm711 zm711 marked this pull request as ready for review June 18, 2025 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deprecations Related to code deprecation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant