feat!: advance lifecycle deprecation from soft to warn

[maelle]

No description provided.

[aviator-app]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was closed without merging. If you still want to merge this PR, re-open it.

---

See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.

[krlmlr]

Happy to run revdepchecks once the build is green.

[aviator-app]

This pull request can't be queued because it's currently a draft.

[maelle]

@krlmlr the build is green now 😇 could you please run revdeps checks? 🙏 thank you!

[krlmlr]

Nice! I'd like to tackle this after the 2.0.0 release. The goal of that release is to use the new C core.

[maelle]

What's the next version number? Could you please run revdeps checks for this branch?

[krlmlr]

For the change from soft to warn, do we really advance the version number?

I feel it's a little too early for that. Should we first move everything to {lifecycle} and give downstream some time to adapt? I suspect most users aren't even aware of the API change.

[maelle]

For the change from soft to warn, do we really advance the version number?

Oh right, no.

I feel it's a little too early for that. Should we first move everything to {lifecycle} and give downstream some time to adapt? I suspect most users aren't even aware of the API change.

Ok.