-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
0.25.0 not committing changes to files other than .bumpversion.toml
#220
Comments
First, thank you for the detailed report. The bump to 0.25.0 was to check for the config file being part of the repository. Meanwhile, I will check the tests and write a regression test if necessary. |
@Makeshift Can you look in the verbose logging if one of the following lines appears:
If you see only If you see any of the other lines, it explains why it didn't update the config file. |
@Makeshift OK, I just realized that I misread your entire bug report. I thought it was changing all files except the config. So, for additional clarification, were the changes to the configuration included in the commit? |
@coordt To confirm, when we run 0.25.0 results in commits that look like this: And 0.24.3 results in commits that (correctly) look like this: I've fixed my local setup and can now replicate this issue locally. If I run $ git status
On branch upgrade-test
nothing to commit, working tree clean
$ bump-my-version bump patch
$ git log -n1
commit 5d422be9db2c4a69573c60ff0600883d5bf1964e (HEAD -> upgrade-test, tag: 7.4.17)
Author: Connor Bell (Makeshift) <[email protected]>
Date: Wed Aug 7 17:23:00 2024 +0100
Bump Version v7.4.16 -> v7.4.17
$ git status
On branch upgrade-test
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: helm/charts/alb-ip-ws-coreapiservice/Chart.yaml
modified: helm/charts/alb-ip-ws-socialapiservice/Chart.yaml
... In the verbose log file, it states that it is adding these files to git, but it isn't:
|
@Makeshift I've created a test that I think mimics your situation. This test passes. Can you review the test to see where I may have got it wrong? If it looks good, I can add additional logging in this branch and you can custom install it locally to get more information. |
@Makeshift Sorry, I found the missing part: I wasn't checking if the files were committed, only changed. Nevermind the previous comment. |
Description
We use bump-my-version as part of our CI pipeline in GitHub Actions. We were installing the latest version, and we noticed that as of 0.25.0, bump-my-version is only committing changes to the
.bumpversion.toml
file and not changes to other files, despite claiming to in the log.What I Did
In the resulting log, I can see that it does find and replace the version in each file that it's meant to (or at least it logs that it does - I don't have access to the filesystem it's making changes on during this log, so I can't actually see if it's made that change):
At the end of the log, I can see that it is adding it to git:
However, the subsequent commit does not contain any changes to this file.
For reference, here's the config in use:
Reverting back to 0.24.3 fixes the issue for us.
I'm currently having some trouble with my local dev environment so I can't provide as much detail as I'd like (eg whether it's actually making any changes to the filesystem), but will try to provide more detail if needed.
The text was updated successfully, but these errors were encountered: