Skip to content
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

feat!: 4.0 release #260

Draft
wants to merge 13 commits into
base: main
Choose a base branch
from
Draft

feat!: 4.0 release #260

wants to merge 13 commits into from

Conversation

fredrikaverpil
Copy link
Owner

@fredrikaverpil fredrikaverpil commented Dec 26, 2024

  • Drop Python 3.8 support.
  • Update type hinting for Python 3.9, fix slew of basedpyright and typing warnings.
  • Remove the hatchling build system. Move to uv for installation.
  • Remove version string from __about__.py but keep functionality by reading version from package metadata.

Closes #257

🚧👷‍♂️

@fredrikaverpil fredrikaverpil self-assigned this Dec 26, 2024
@fredrikaverpil fredrikaverpil force-pushed the v4.0 branch 4 times, most recently from bae48c8 to 7fde3a2 Compare December 26, 2024 23:04
@fredrikaverpil fredrikaverpil changed the title Changes for v4.0 feat!: slew of backwards-compat breaking changes Dec 26, 2024
@fredrikaverpil fredrikaverpil force-pushed the v4.0 branch 12 times, most recently from 0db9d06 to 9db1706 Compare December 27, 2024 00:26
@fredrikaverpil fredrikaverpil changed the title feat!: slew of backwards-compat breaking changes feat!: 4.0 release Dec 27, 2024
@fredrikaverpil fredrikaverpil force-pushed the v4.0 branch 5 times, most recently from 7a62cc9 to d985833 Compare December 27, 2024 00:58
@fredrikaverpil fredrikaverpil force-pushed the v4.0 branch 2 times, most recently from 1f0658f to dc1420c Compare December 27, 2024 01:07
@fredrikaverpil fredrikaverpil force-pushed the v4.0 branch 14 times, most recently from f34ad0c to aaafda9 Compare December 27, 2024 02:19
Copy link

github-actions bot commented Jan 3, 2025

This PR has been open for 7 days with no activity. Remove the stale label or add a comment or it will be closed in 3 days.

@github-actions github-actions bot added the Stale label Jan 3, 2025
@fredrikaverpil fredrikaverpil added pinned Won't be taken into staleness consideration and removed Stale labels Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pinned Won't be taken into staleness consideration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Creosote 4.0 heads-up
1 participant