diff options
| author | robot-piglet <robot-piglet@yandex-team.com> | 2024-07-20 07:38:40 +0300 |
|---|---|---|
| committer | robot-piglet <robot-piglet@yandex-team.com> | 2024-07-20 07:58:13 +0300 |
| commit | 7d21c95992e12e49a9afe45263936a45fb902b6e (patch) | |
| tree | 567f7119eaccd4c2dfd9be500066a7b904cc0279 /contrib/python/fonttools/README.rst | |
| parent | 1eafc358f721395d1eac1a4480f51ee78c966485 (diff) | |
| download | ydb-7d21c95992e12e49a9afe45263936a45fb902b6e.tar.gz | |
Intermediate changes
Diffstat (limited to 'contrib/python/fonttools/README.rst')
| -rw-r--r-- | contrib/python/fonttools/README.rst | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/contrib/python/fonttools/README.rst b/contrib/python/fonttools/README.rst index 2274fbdc69..b604ea7ca5 100644 --- a/contrib/python/fonttools/README.rst +++ b/contrib/python/fonttools/README.rst @@ -232,7 +232,8 @@ How to make a new release 2) Use semantic versioning to decide whether the new release will be a 'major', 'minor' or 'patch' release. It's usually one of the latter two, depending on whether new backward compatible APIs were added, or simply some bugs were fixed. -3) Run ``python setup.py release`` command from the tip of the ``main`` branch. +3) From inside a venv, first do ``pip install -r dev-requirements.txt``, then run + the ``python setup.py release`` command from the tip of the ``main`` branch. By default this bumps the third or 'patch' digit only, unless you pass ``--major`` or ``--minor`` to bump respectively the first or second digit. This bumps the package version string, extracts the changes since the latest |