Skip to main content

EN

RU

A simple version based on git/gh.

If there have been no commits or uncommitted changes since the most recent tag, the version from the tag is used as the project version.

If the latest tag is final release, then the last part is incremented by 1 and alpha 0 is added.

If the latest tag is pre-release, the pre-release number is incremented by 1.

used:

add gitversion_simple[setuptools] in build-system.requires (in pyproject.toml)

[build-system]
requires = [
  "setuptools>=81.0.0",
  "gitversion_simple[setuptools]~=3.0",
]

If you use a different backend for the build:

  1. Add gitversion_simple instead of gitversion_simple[setuptools]
  2. Manually call gitversion_simple.version.get_version or gitversion_simple.version.get_with_config
  3. *If this is a public builder, create a PR/issue to add

This project is based on vcs-versioning, so it supports the entry point vcs_versioning.discover_workdir.

If the file pyproject.toml is not located in the root of the repository, then specify the path to the root of the repository in the vcs_root parameter in the tool.gitversion_simple table.

For the following repository

git_folder/
├─ .git/
├─ my_project
│  ├─ ...
│  └─ pyproject.toml
├─ my_project2
│  ├─ ...
│  └─ pyproject.toml
└ README.md

Add to both pyproject.toml files

[tool.gitversion_simple]
vcs_root = ".."

examples:

last tag version
v1.0.0 1.0.1
v1.0.0a1 1.0.0a2
v1.0.0b2 1.0.0b3
v1.0 1.1
v1.2.3.4 1.2.3.5
v26.1 26.2

RU

EN

Простая версия, основанная на git/gh.

Если с момента создания последнего тега не было никаких фиксаций или незафиксированных изменений, в качестве версии проекта используется версия из тега.

Если последним тегом является финальным релизом, то последняя часть увеличивается на 1 и добавляется alpha 0.

Если последним тегом является предварительным релизом, то номер предварительного выпуска увеличивается на 1.

Использование:

добавьте gitversion_simple[setuptools] в build-system.requires (в файл pyproject.toml)

[build-system]
requires = [
  "setuptools>=81.0.0",
  "gitversion_simple[setuptools]~=3.0",
]

Если вы используете другой бекенд для сборки:

  1. Добавьте gitversion_simple, вместо gitversion_simple[setuptools]
  2. Вручную вызовите gitversion_simple.version.get_version или gitversion_simple.version.get_with_config
  3. *Если это публичный сборщик, создайте PR/issue на добавление

Этот проект основан на vcs-versioning, поэтому он поддерживает точку входа vcs_versioning.discover_workdir.

Если файл pyproject.toml находиться не в корне репозитория, то укажите путь до корня репозитория в параметре vcs_root в таблице tool.gitversion_simple.

Для следующего репозитория

git_folder/
├─ .git/
├─ my_project
│  ├─ ...
│  └─ pyproject.toml
├─ my_project2
│  ├─ ...
│  └─ pyproject.toml
└ README.md

Добавьте в оба файла pyproject.toml

[tool.gitversion_simple]
vcs_root = ".."

примеры:

последний тег версия
v1.0.0 1.0.1
v1.0.0a1 1.0.0a2
v1.0.0b2 1.0.0b3
v1.0 1.1
v1.2.3.4 1.2.3.5
v26.1 26.2

Metadata

Release files for gitversion-simple 3.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for gitversion-simple 3.0.0
File Size Uploaded
gitversion_simple-3.0.0.tar.gz 7.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for gitversion-simple 3.0.0
File Interpreter ABI Platform
gitversion_simple-3.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 15.1 kB

Release files / gitversion_simple-3.0.0.tar.gz

Download URL gitversion_simple-3.0.0.tar.gz
Size 7.4 kB
Tags Source
SHA-256 checksum
How to use checksums
6f1afa1dac9709030115db3c9c98d8fda0fd76f413d5ee3e3465e2e2a1017171
BLAKE2b-256 checksum
How to use checksums
a9b8953023a79b8a11dcb6e441e97a48e29908dcfd2d2eff074ac49fc637fef7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.

Transparency log

Release files / gitversion_simple-3.0.0-py3-none-any.whl

Download URL gitversion_simple-3.0.0-py3-none-any.whl
Size 7.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9a19751ee076136e9c07c94faccac6cfe206374b4f2826c20502e362c25eb60f
BLAKE2b-256 checksum
How to use checksums
bfef72235a364f80ca22216d5c1b9cfc2985f23882a8606aa890c55f3c45260d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

3.0.0 This release

2 release files

2.0.1

2 release files

2.0.0

2 release files

1.1.0

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page