Skip to content

Conversation

@hauleth
Copy link
Contributor

@hauleth hauleth commented Jan 17, 2025

No description provided.

@hauleth hauleth requested a review from a team as a code owner January 17, 2025 11:14
@hauleth hauleth force-pushed the chore/remove-version-bump-check branch from 4c7af4e to 9259b60 Compare January 17, 2025 11:22
Copy link
Contributor

@chasers chasers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hauleth why is this important right now?

@hauleth
Copy link
Contributor Author

hauleth commented Jan 20, 2025

@chasers it is not important right now. It is just opened for the future. Should I close it and open it later?

@chasers
Copy link
Contributor

chasers commented Jan 22, 2025

Yeah sure go ahead and close for now. We can revisit all version stuff after we get v2 out.

@hauleth hauleth force-pushed the chore/remove-version-bump-check branch from 9259b60 to 2c0cd6d Compare January 23, 2025 14:53
@hauleth hauleth force-pushed the chore/remove-version-bump-check branch from 2c0cd6d to e8e2733 Compare January 24, 2025 16:25
@hauleth hauleth closed this Jan 24, 2025
@hauleth
Copy link
Contributor Author

hauleth commented Jan 24, 2025

I closed, but recently it was really painful to keep that file up to date. Especially with sheer amount of little changes, especially one that aren't really related to application code.

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.

3 participants