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

Release 2.0 #176

Closed
wants to merge 2 commits into from
Closed

Release 2.0 #176

wants to merge 2 commits into from

Conversation

mzbroch
Copy link
Contributor

@mzbroch mzbroch commented Feb 27, 2024

@glennmatthews
Copy link
Contributor

glennmatthews commented Feb 27, 2024

Can/should we switch to a proper major/minor versioning scheme at this point? I.e. release "1.0" from ltm-1.6 and "2.0" from main?

@mzbroch mzbroch force-pushed the mzbroch/release-0.21 branch from c6e3c57 to 38135d2 Compare February 27, 2024 19:39
@glennmatthews
Copy link
Contributor

Downside of not pinning dev dependencies - looks like your lockfile updates brought in a newer version of Black with different opinions on formatting.

@mzbroch mzbroch changed the title Release 0.21 Release 2.0 Feb 27, 2024
@mzbroch
Copy link
Contributor Author

mzbroch commented Feb 27, 2024

Downside of not pinning dev dependencies - looks like your lockfile updates brought in a newer version of Black with different opinions on formatting.

Just fixed black issues, please re-review @glennmatthews

@mzbroch mzbroch closed this Feb 27, 2024
@mzbroch mzbroch deleted the mzbroch/release-0.21 branch February 27, 2024 19:53
@mzbroch
Copy link
Contributor Author

mzbroch commented Feb 27, 2024

Closed and re-opened in #178

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

Successfully merging this pull request may close these issues.

2 participants