You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 20, 2026. It is now read-only.
First, thanks for this nice tool. I exactly understand your motivation for switching from bumpversion and I admit that solving various workflow and integration issues (like incorporating change log generation in the same transaction) became nice and easy with tbump.
Now to the issue.
I'm using the tool to support version tracking for project, where a single line match is not ambiguity-free. Eg. the version is stored as:
[[package]]
name = "my-project"
version = "1.1.0"
along with references to other thirdparty packages, let's say:
[[package]]
name = "rustc-hash"
version = "1.1.0"
[[package]]
name = "scopeguard"
version = "1.1.0"
Making a search formula in tbump.toml to bump only the my-project version string to 1.2.0 is currently not possible IMO.
I suggest supporting multi-line regex, so things like \n line ending could be added to make unique matches possible in situations like this:
First, thanks for this nice tool. I exactly understand your motivation for switching from
bumpversionand I admit that solving various workflow and integration issues (like incorporating change log generation in the same transaction) became nice and easy withtbump.Now to the issue.
I'm using the tool to support version tracking for project, where a single line match is not ambiguity-free. Eg. the version is stored as:
along with references to other thirdparty packages, let's say:
Making a search formula in
tbump.tomlto bump only themy-projectversion string to 1.2.0 is currently not possible IMO.I suggest supporting multi-line regex, so things like
\nline ending could be added to make unique matches possible in situations like this: