Skip to content

Improvement: Single source of version truth #424

Closed
@jacksbox

Description

@jacksbox

Description

Note: This ticket is purely about implementation.
Currently the version numbers are determined via multiple ways depending on the config and the called method.
Depending if get_current_version, get_next_version, and more, different ways to determine this version are used:
based on tags, based on parsed commit messages, the version file (and maybe more?).
I understand the need for this in the current implementation, but it feels a bit error prone and I think it would make the code easier and cleaner if we could come up with a single way how versions are determined / parsed / found.

I would like to open a discussion about this...

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureA new feature or a feature requeststale

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions