Skip to content

chore: use @typescript-eslint v8 in development #1757

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

Merged
merged 3 commits into from
Jun 13, 2025
Merged

Conversation

G-Rath
Copy link
Collaborator

@G-Rath G-Rath commented Jun 11, 2025

Building on #1755, this lets us address a few things while still supporting the older versions - I'll do a dedicated PR marking the properties on unbound-method as deprecated to trigger a new release before the next major

@G-Rath G-Rath force-pushed the support-strings-more branch from 08763b7 to bcbc889 Compare June 13, 2025 04:14
@G-Rath G-Rath force-pushed the support-strings-more branch from bcbc889 to 784ad1b Compare June 13, 2025 04:17
@G-Rath G-Rath force-pushed the support-strings-more branch from 784ad1b to 027aa0e Compare June 13, 2025 04:21
@G-Rath G-Rath changed the title feat: confirm @typescript-eslint v8 compatibility chore: use @typescript-eslint v8 in development Jun 13, 2025
@G-Rath G-Rath marked this pull request as ready for review June 13, 2025 04:22
@G-Rath G-Rath merged commit 51d39cc into main Jun 13, 2025
59 checks passed
@G-Rath G-Rath deleted the support-strings-more branch June 13, 2025 04:29
Copy link

🎉 This PR is included in version 28.14.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant