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

Version bump to 0.2.0 #126

Merged
merged 1 commit into from
Mar 28, 2024
Merged

Version bump to 0.2.0 #126

merged 1 commit into from
Mar 28, 2024

Conversation

kobalicek
Copy link
Contributor

No description provided.

check-version.py Outdated Show resolved Hide resolved
include/miniocpp/config.h Show resolved Hide resolved
vcpkg.json Show resolved Hide resolved
@kobalicek
Copy link
Contributor Author

@balamurugana I think that if you want to have the version number somewhat more manageable, I would suggest extending the script to "patch" all the files that contain a version, and then we can even have a separate workflow to just do the version bump, and have that automated.

However, since this project has only 4 published versions yet, I'm just unsure whether it would pay off. I would reconsider if we want to release more often, let's say on a weekly basis, which I'm not sure is going to materialize considering that there is not a lot of changes monthly.

@kobalicek kobalicek merged commit 2132b81 into main Mar 28, 2024
4 checks passed
@kobalicek kobalicek deleted the version_0_2 branch March 28, 2024 14:06
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