Skip to content

Dependencies versions in pyproject.toml altered casually #220

@Tammura

Description

@Tammura

Hi all,

I've encountered an issue twice while using the CLI to release a new patch with the bumpversion patch pyproject.toml command. It seems that this command not only updates the project version but also inadvertently changes the versions of project dependencies.

Before running cli command:

# pyproject.toml
[build-system]
requires = ["setuptools>=61.0.1", "wheel"]

dependencies = [
    "python-dotenv>=1.0.1",
    ...
]

[tool.bumpver]
current_version = "1.0.1"
version_pattern = "MAJOR.MINOR.PATCH"
commit_message = "bump version {old_version} -> {new_version}"
tag_message = "{new_version}"
tag_scope = "default"
commit = true
tag = true
push = false
...
#.bumpversion.cfg
[bumpversion]
current_version = 1.0.1
commit = True
tag = True
tag_name = {new_version}

After command execution: bumpversion patch pyproject.toml

# pyproject.toml
[build-system]
requires = ["setuptools>=61.0.2", "wheel"] # setuptools version updated to 61.0.2

dependencies = [
    "python-dotenv>=1.0.2", # python-dotenv version updated to 1.0.2
    ...
]

[tool.bumpver]
current_version = "1.0.2"
version_pattern = "MAJOR.MINOR.PATCH"
commit_message = "bump version {old_version} -> {new_version}"
tag_message = "{new_version}"
tag_scope = "default"
commit = true
tag = true
push = false
...
#.bumpversion.cfg
[bumpversion]
current_version = 1.0.2
commit = True
tag = True
tag_name = {new_version}

Anyone facing the same problem? Any idea on how to fix it?
Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions