Skip to content

Resolve Dev Versioning Problem #429

@dayo09

Description

@dayo09

What?

Current versioning is incorrect as we've been keep using 0.1.0.devYYMMDD even though we released 0.1.0.
It is caused by forgetting bump after 0.1.0 release.

Let's start using 0.2.0.devYYMMDD tag.

Additionally, I suggest we use pyproject.toml instead of setup.py which is modern standard of python packaging.

details

Steps

  • tag 0.2.0.devYYMMDD
  • transit to pyproject.toml
  • use versioiningit

Need Updates

  • publish-nightly workflow
  • publish-official workflow

Keep date-based dev versioning

[tool.versioningit]
# 날짜 형식을 'YYMMDD'로 지정 (예: 260107)
[tool.versioningit.vcs]
method = "git"
match = ["v*"]
default-tag = "v0.0.0"

[tool.versioningit.format]
# 태그가 붙은 정식 릴리즈가 아닐 때(개발 중일 때)의 포맷
# {next_version}: 다음 예상 버전 (0.2.0)
# .dev{committer_date:%y%m%d}: .dev + 날짜
distance = "{next_version}.dev{committer_date:%y%m%d}"

# 소스코드 수정 후 커밋 안 했을 때 (선택 사항)
dirty = "{next_version}.dev{committer_date:%y%m%d}+dirty"
distance-dirty = "{next_version}.dev{committer_date:%y%m%d}+dirty"

[tool.versioningit.next-version]
method = "minor" # 0.1.0 이후면 자동으로 0.2.0을 타겟팅

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions