Metadata-Version: 2.4
Name: tinysemver
Version: 3.1.1
Summary: Deprecated: Semantic Versioning from Conventional Commits in one Python file
Author-email: Ash Vardanian <1983160+ashvardanian@users.noreply.github.com>
License:                                  Apache License
                                   Version 2.0, January 2004
                                http://www.apache.org/licenses/
        
           TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
        
           1. Definitions.
        
              "License" shall mean the terms and conditions for use, reproduction,
              and distribution as defined by Sections 1 through 9 of this document.
        
              "Licensor" shall mean the copyright owner or entity authorized by
              the copyright owner that is granting the License.
        
              "Legal Entity" shall mean the union of the acting entity and all
              other entities that control, are controlled by, or are under common
              control with that entity. For the purposes of this definition,
              "control" means (i) the power, direct or indirect, to cause the
              direction or management of such entity, whether by contract or
              otherwise, or (ii) ownership of fifty percent (50%) or more of the
              outstanding shares, or (iii) beneficial ownership of such entity.
        
              "You" (or "Your") shall mean an individual or Legal Entity
              exercising permissions granted by this License.
        
              "Source" form shall mean the preferred form for making modifications,
              including but not limited to software source code, documentation
              source, and configuration files.
        
              "Object" form shall mean any form resulting from mechanical
              transformation or translation of a Source form, including but
              not limited to compiled object code, generated documentation,
              and conversions to other media types.
        
              "Work" shall mean the work of authorship, whether in Source or
              Object form, made available under the License, as indicated by a
              copyright notice that is included in or attached to the work
              (an example is provided in the Appendix below).
        
              "Derivative Works" shall mean any work, whether in Source or Object
              form, that is based on (or derived from) the Work and for which the
              editorial revisions, annotations, elaborations, or other modifications
              represent, as a whole, an original work of authorship. For the purposes
              of this License, Derivative Works shall not include works that remain
              separable from, or merely link (or bind by name) to the interfaces of,
              the Work and Derivative Works thereof.
        
              "Contribution" shall mean any work of authorship, including
              the original version of the Work and any modifications or additions
              to that Work or Derivative Works thereof, that is intentionally
              submitted to Licensor for inclusion in the Work by the copyright owner
              or by an individual or Legal Entity authorized to submit on behalf of
              the copyright owner. For the purposes of this definition, "submitted"
              means any form of electronic, verbal, or written communication sent
              to the Licensor or its representatives, including but not limited to
              communication on electronic mailing lists, source code control systems,
              and issue tracking systems that are managed by, or on behalf of, the
              Licensor for the purpose of discussing and improving the Work, but
              excluding communication that is conspicuously marked or otherwise
              designated in writing by the copyright owner as "Not a Contribution."
        
              "Contributor" shall mean Licensor and any individual or Legal Entity
              on behalf of whom a Contribution has been received by Licensor and
              subsequently incorporated within the Work.
        
           2. Grant of Copyright License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              copyright license to reproduce, prepare Derivative Works of,
              publicly display, publicly perform, sublicense, and distribute the
              Work and such Derivative Works in Source or Object form.
        
           3. Grant of Patent License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              (except as stated in this section) patent license to make, have made,
              use, offer to sell, sell, import, and otherwise transfer the Work,
              where such license applies only to those patent claims licensable
              by such Contributor that are necessarily infringed by their
              Contribution(s) alone or by combination of their Contribution(s)
              with the Work to which such Contribution(s) was submitted. If You
              institute patent litigation against any entity (including a
              cross-claim or counterclaim in a lawsuit) alleging that the Work
              or a Contribution incorporated within the Work constitutes direct
              or contributory patent infringement, then any patent licenses
              granted to You under this License for that Work shall terminate
              as of the date such litigation is filed.
        
           4. Redistribution. You may reproduce and distribute copies of the
              Work or Derivative Works thereof in any medium, with or without
              modifications, and in Source or Object form, provided that You
              meet the following conditions:
        
              (a) You must give any other recipients of the Work or
                  Derivative Works a copy of this License; and
        
              (b) You must cause any modified files to carry prominent notices
                  stating that You changed the files; and
        
              (c) You must retain, in the Source form of any Derivative Works
                  that You distribute, all copyright, patent, trademark, and
                  attribution notices from the Source form of the Work,
                  excluding those notices that do not pertain to any part of
                  the Derivative Works; and
        
              (d) If the Work includes a "NOTICE" text file as part of its
                  distribution, then any Derivative Works that You distribute must
                  include a readable copy of the attribution notices contained
                  within such NOTICE file, excluding those notices that do not
                  pertain to any part of the Derivative Works, in at least one
                  of the following places: within a NOTICE text file distributed
                  as part of the Derivative Works; within the Source form or
                  documentation, if provided along with the Derivative Works; or,
                  within a display generated by the Derivative Works, if and
                  wherever such third-party notices normally appear. The contents
                  of the NOTICE file are for informational purposes only and
                  do not modify the License. You may add Your own attribution
                  notices within Derivative Works that You distribute, alongside
                  or as an addendum to the NOTICE text from the Work, provided
                  that such additional attribution notices cannot be construed
                  as modifying the License.
        
              You may add Your own copyright statement to Your modifications and
              may provide additional or different license terms and conditions
              for use, reproduction, or distribution of Your modifications, or
              for any such Derivative Works as a whole, provided Your use,
              reproduction, and distribution of the Work otherwise complies with
              the conditions stated in this License.
        
           5. Submission of Contributions. Unless You explicitly state otherwise,
              any Contribution intentionally submitted for inclusion in the Work
              by You to the Licensor shall be under the terms and conditions of
              this License, without any additional terms or conditions.
              Notwithstanding the above, nothing herein shall supersede or modify
              the terms of any separate license agreement you may have executed
              with Licensor regarding such Contributions.
        
           6. Trademarks. This License does not grant permission to use the trade
              names, trademarks, service marks, or product names of the Licensor,
              except as required for reasonable and customary use in describing the
              origin of the Work and reproducing the content of the NOTICE file.
        
           7. Disclaimer of Warranty. Unless required by applicable law or
              agreed to in writing, Licensor provides the Work (and each
              Contributor provides its Contributions) on an "AS IS" BASIS,
              WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
              implied, including, without limitation, any warranties or conditions
              of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
              PARTICULAR PURPOSE. You are solely responsible for determining the
              appropriateness of using or redistributing the Work and assume any
              risks associated with Your exercise of permissions under this License.
        
           8. Limitation of Liability. In no event and under no legal theory,
              whether in tort (including negligence), contract, or otherwise,
              unless required by applicable law (such as deliberate and grossly
              negligent acts) or agreed to in writing, shall any Contributor be
              liable to You for damages, including any direct, indirect, special,
              incidental, or consequential damages of any character arising as a
              result of this License or out of the use or inability to use the
              Work (including but not limited to damages for loss of goodwill,
              work stoppage, computer failure or malfunction, or any and all
              other commercial damages or losses), even if such Contributor
              has been advised of the possibility of such damages.
        
           9. Accepting Warranty or Additional Liability. While redistributing
              the Work or Derivative Works thereof, You may choose to offer,
              and charge a fee for, acceptance of support, warranty, indemnity,
              or other liability obligations and/or rights consistent with this
              License. However, in accepting such obligations, You may act only
              on Your own behalf and on Your sole responsibility, not on behalf
              of any other Contributor, and only if You agree to indemnify,
              defend, and hold each Contributor harmless for any liability
              incurred by, or claims asserted against, such Contributor by reason
              of your accepting any such warranty or additional liability.
        
           END OF TERMS AND CONDITIONS
        
           APPENDIX: How to apply the Apache License to your work.
        
              To apply the Apache License to your work, attach the following
              boilerplate notice, with the fields enclosed by brackets "[]"
              replaced with your own identifying information. (Don't include
              the brackets!)  The text should be enclosed in the appropriate
              comment syntax for the file format. We also recommend that a
              file or class name and description of purpose be included on the
              same "printed page" as the copyright notice for easier
              identification within third-party archives.
        
           Copyright [yyyy] [name of copyright owner]
        
           Licensed under the Apache License, Version 2.0 (the "License");
           you may not use this file except in compliance with the License.
           You may obtain a copy of the License at
        
               http://www.apache.org/licenses/LICENSE-2.0
        
           Unless required by applicable law or agreed to in writing, software
           distributed under the License is distributed on an "AS IS" BASIS,
           WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
           See the License for the specific language governing permissions and
           limitations under the License.
        
Project-URL: Homepage, https://pypi.org/project/tinysemver/
Project-URL: Documentation, https://github.com/ashvardanian/TinySemVer/blob/main/README.md
Project-URL: Repository, https://github.com/ashvardanian/TinySemVer.git
Project-URL: Issues, https://github.com/ashvardanian/TinySemVer/issues
Project-URL: Changelog, https://github.com/ashvardanian/TinySemVer/blob/main/CHANGELOG.md
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: Topic :: Software Development :: Build Tools
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Programming Language :: Python :: 3.14
Requires-Python: >=3.11
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: rich>=13.8.0
Provides-Extra: test
Requires-Dist: pytest>=7.0.0; extra == "test"
Requires-Dist: pytest-cov>=4.0.0; extra == "test"
Requires-Dist: pytest-mock>=3.10.0; extra == "test"
Provides-Extra: dev
Requires-Dist: pytest>=7.0.0; extra == "dev"
Requires-Dist: pytest-cov>=4.0.0; extra == "dev"
Requires-Dist: pytest-mock>=3.10.0; extra == "dev"
Requires-Dist: ruff>=0.1.0; extra == "dev"
Requires-Dist: mypy>=1.0.0; extra == "dev"
Requires-Dist: black>=23.0.0; extra == "dev"
Dynamic: license-file

# TinySemVer

![TinySemVer Banner](https://github.com/ashvardanian/ashvardanian/blob/master/repositories/TinySemVer.jpg)

> [!WARNING]
> TinySemVer is deprecated and archived.
> Automated versioning needs a CI credential that can push past branch protection, which in practice means long-lived tokens readable by every workflow and third-party Action in every repository.
> That attack surface grows far faster than the value of automatic version bumps.
> Bump versions by hand in a `Release: vX.Y.Z` commit, publish with `gh release create`, and let CI publish on `release: published` through trusted publishing.

__TinySemVer__ turns [Conventional Commits](https://www.conventionalcommits.org/) into [Semantic Versioning](https://semver.org/) releases from a single short Python file.
It reads the commits since the last tag, picks the next version, patches it into every file you name, extends the changelog, commits, tags and optionally publishes a GitHub release.

```sh
$ uvx tinysemver --dry-run --verbose
> Current version: 1.2.2
> Next version: 1.3.0
```

`uvx` runs it straight from PyPI, while `pip install tinysemver` or `uv tool install tinysemver` keep it installed.
A dry run changes nothing, so it's safe anywhere.

## Commit Verbs

The first word of each commit title decides the bump, in any case, followed by a colon or a space:

- Major: `breaking`, `break`, `major`.
- Minor: `feature`, `feat`, `minor`, `add`, `new`.
- Patch: `fix`, `patch`, `bug`, `improve`, `docs`, `make`.

A commit matching none of them stops the release, and merge commits are skipped.
Replace any list with `--major-verbs`, `--minor-verbs` or `--patch-verbs`.

## Command Line

Each file that embeds the version takes a path and a regular expression with exactly one capturing group, which receives the new version:

```sh
$ tinysemver --verbose \
    --changelog-file 'CHANGELOG.md' \
    --version-file 'VERSION' \
    --update-version-in 'pyproject.toml' '^version = "(\d+\.\d+\.\d+)"' \
    --update-version-in 'package.json' '"version": "(\d+\.\d+\.\d+)"' \
    --update-major-version-in 'include/project.h' '^#define PROJECT_VERSION_MAJOR (\d+)' \
    --update-minor-version-in 'include/project.h' '^#define PROJECT_VERSION_MINOR (\d+)' \
    --update-patch-version-in 'include/project.h' '^#define PROJECT_VERSION_PATCH (\d+)' \
    --github-repository 'owner/project' \
    --push
```

Prefer strict groups like `(\d+\.\d+\.\d+)` over `(.*)`.
Without `--push`, the release commit and tag stay local, and `git reset --soft HEAD~1` undoes the commit.
Run `tinysemver --help` for every flag.

## GitHub Action

The [GitHub Action](https://github.com/marketplace/actions/tinysemver) takes the same settings as inputs, writing patterns as `path:regex` lines in a `|` block.
A dry run on every pull request catches a commit title without a verb, or a pattern that stopped matching:

```yaml
- uses: actions/checkout@v7
  with:
    fetch-depth: 0 # TinySemVer needs the tags
- uses: ashvardanian/tinysemver@v3
  with:
    dry-run: "true"
    verbose: "true"
    version-file: "VERSION"
    update-version-in: |
      pyproject.toml:^version = "(\d+\.\d+\.\d+)"
      package.json:"version": "(\d+\.\d+\.\d+)"
```

Pushing from CI takes `push: "true"` and a `github-token` that bypasses your branch protection, with `persist-credentials: false` on the checkout.
That token is the attack surface the warning above describes.

## Release Candidates

TinySemVer never invents pre-releases, but it honors a `-rc.N` set by hand in the version file, to let people opt into a project before its API is stable.
While the version file holds `3.0.0-rc.1`, the next release is exactly `3.0.0`, whatever the verbs say, and its changelog lists every commit since the last final tag.
Pre-release tags never serve as the base, and the `-rc.N` suffix is stripped from every patched file, so the usual `(\d+\.\d+\.\d+)` patterns keep matching.
A candidate that isn't above the last final tag stops the release, and other pre-release or build suffixes are rejected.

## Moving Tags

With `--push-moving-tags`, or `push-moving-tags: "true"` in the Action, each `v3.1.0` release also moves the `v3` and `v3.1` aliases, the way GitHub Actions are usually pinned:

```yaml
uses: ashvardanian/tinysemver@v3       # non-breaking updates
uses: ashvardanian/tinysemver@v3.1     # patch updates
uses: ashvardanian/tinysemver@v3.1.0   # never changes
```

Moving a tag is a force-push, so it needs permission to bypass tag protection.
If an alias can't be pushed, TinySemVer warns and moves on, because the release itself is already published.

## Why Another Tool

I used to release my 10+ projects with [semantic-release](https://github.com/semantic-release/semantic-release).
Then a breaking change deep in its dependencies broke all of their CI pipelines for a month, affecting dozens of companies using those libraries.
Tracing it meant wading through __363K lines of JavaScript__:

```sh
$ .../node_modules$ cloc .
   10751 text files.
    7809 unique files.
    3498 files ignored.

github.com/AlDanial/cloc v 1.90  T=2.96 s (2450.6 files/s, 300331.1 lines/s)
--------------------------------------------------------------------------------
Language                      files          blank        comment           code
--------------------------------------------------------------------------------
JavaScript                     4902          48080          81205         363424
TypeScript                      732           7008          73034          79367
...                             ...            ...            ...            ...
--------------------------------------------------------------------------------
SUM:                           7256          90782         164390         634071
--------------------------------------------------------------------------------
```

TinySemVer is one Python file with about 600 lines of code, and `rich` for colored output as its only dependency.

## What's Missing

- Commit scopes, like `feat(scope): add new feature`, which make little sense for most projects.
- GenAI.

TinySemVer accepts only `MAJOR.MINOR.PATCH` and a hand-set `-rc.N`, while SemVer 2.0 allows [many more forms](https://regex101.com/r/Ly7O1x/3/), like `1.0.0-alpha.beta.1` or `2.0.0+build.1848`.

## Real-World Example

[USearch](https://github.com/unum-cloud/usearch) has bindings to 10 programming languages, and its version lives in a dozen files:

```sh
$ tinysemver --dry-run --verbose \
    --version-file 'VERSION' \
    --update-version-in 'package.json' '"version": "(\d+\.\d+\.\d+)"' \
    --update-version-in 'CITATION.cff' '^version: (\d+\.\d+\.\d+)' \
    --update-version-in 'Cargo.toml' '^version = "(\d+\.\d+\.\d+)"' \
    --update-version-in 'wasmer.toml' '^version = "(\d+\.\d+\.\d+)"' \
    --update-version-in 'conanfile.py' 'version = "(\d+\.\d+\.\d+)"' \
    --update-version-in 'java/README.md' "usearchVersion = '(\d+\.\d+\.\d+)'" \
    --update-version-in 'java/README.md' "version: '(\d+\.\d+\.\d+)'" \
    --update-version-in 'README.md' 'version = {(\d+\.\d+\.\d+)}' \
    --update-version-in 'csharp/nuget/nuget-package.props' '>(\d+\.\d+\.\d+)</Version>' \
    --update-version-in 'CMakeLists.txt' 'VERSION (\d+\.\d+\.\d+)' \
    --update-major-version-in 'include/usearch/index.hpp' '^#define USEARCH_VERSION_MAJOR (\d+)' \
    --update-minor-version-in 'include/usearch/index.hpp' '^#define USEARCH_VERSION_MINOR (\d+)' \
    --update-patch-version-in 'include/usearch/index.hpp' '^#define USEARCH_VERSION_PATCH (\d+)'
```
