| Name | foxy-project JSON |
| Version |
2.4.1
JSON |
| download |
| home_page | |
| Summary | A tool which generates a changelog and manage version for any git repository using conventional commits specification |
| upload_time | 2024-02-11 09:33:24 |
| maintainer | |
| docs_url | None |
| author | |
| requires_python | >=3.8 |
| license | |
| keywords |
changelog
git
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# 🦊 Foxy project
> [!IMPORTANT]
> This repository is a fork of [auto-changelog](https://github.com/KeNaCo/auto-changelog).
> I decided to do it because auto-changelog is not maintained anymore and I need some changes for my personal usage.
> I will publish these changes for everyone to use but I do not promise to answer to feature request and bug fixes.
>
> **Sadly I do not have time to provide steps to contribute and not everything will be tested.**
| | |
| --- | --- |
| Package | [](https://pypi.org/project/foxy-project/) [](https://pypi.org/project/foxy-project/) [](https://pypi.org/project/foxy-project/) |
| Meta | [](https://github.com/pypa/hatch) [](https://github.com/astral-sh/ruff) [](https://github.com/python/mypy) [](https://spdx.org/licenses/) |
A tool which generates a changelog and manage version for any git repository using [`conventional commits`](https://www.conventionalcommits.org/en/v1.0.0/) specification.
- [Installation](#installation)
- [Changelog generation](#changelog-generation)
- [Add to an existing changelog](#add-to-an-existing-changelog)
- [Version management](#version-management)
- [pep440-conventional-commit-foxy](#pep440-conventional-commit-foxy)
- [semver-conventional-commit-foxy](#semver-conventional-commit-foxy)
- [calendar-conventional-commit-foxy](#calendar-conventional-commit-foxy)
- [Configuration](#configuration)
- [Python project](#python-project)
- [Hatch](#hatch)
- [Other projects](#other-projects)
- [Available configurations](#available-configurations)
- [Github actions](#github-actions)
- [Command line interface](#command-line-interface)
- [foxy-project changelog](#foxy-project-changelog)
- [foxy-project version](#foxy-project-version)
## Installation
It is recommanded to install this tool with [`pipx`](https://github.com/pypa/pipx) to install it in a isolated environments:
```console
pipx install foxy-project
```
## Changelog generation
Runnning the following command in the working environment will generate the project's changelog according to its commit history.
```console
foxy-project changelog
```
### Add to an existing changelog
If you’d like to keep an existing changelog below your generated one, just add `<!-- foxy-changelog-above -->` to your current changelog.
The generated changelog will be added above this token, and anything below will remain.
> [!TIP]
> This is quite useful when changing the tag pattern (e.g. from semver to calendar) used to version a project or to help keeping an old manually generated changelog when integrated conventional commit to a project.
## Version management
`foxy-project` is providing support to automatically generate the version of your python project according to its commit history.
The management is based on [setuptools_scm](https://github.com/pypa/setuptools_scm) and [conventional commit](https://www.conventionalcommits.org/en/v1.0.0/).
As defined in the conventional commit specification:
>- The type `feat` MUST be used when a commit adds a new feature to your application or library.
>- The type `fix` MUST be used when a commit represents a bug fix for your application.
Runnning the following command in the working environment will print the project's version the according to its commit history.
```console
foxy-project version
```
> [!TIP]
> It is also possible to generate a file with the generated version. This behavior is deactivated by default.
>
> Use the `version_file` and `version_file_template` option to configure the generation.
> Embedded templates for `.py` and `.txt` are available. A custom template needs to be provided for other type of file.
`foxy-project` is providing three version schemas which control how the version is incremented.
### pep440-conventional-commit-foxy
Based on [PEP440](https://peps.python.org/pep-0440/). Selected by default.
Logic:
A commit with `feat` type activates an increment of the minor, otherwise all other types will activate an increment of the patch.
Then appends `.devN` where `N` is the distance between the current commit and the previous tag.
> [!WARNING]
> Breaking changes and pre-release is not supported yet.
### semver-conventional-commit-foxy
Based on [semver](https://semver.org/lang/fr/).
Logic:
A commit with `feat` type activates an increment of the minor, otherwise all other types will activate an increment of the patch.
Then appends `-devN` where `N` is the distance between the current commit and the previous tag.
> [!WARNING]
> Breaking changes and pre-release with other name than `dev` is not supported yet.
### calendar-conventional-commit-foxy
To manage version based on the calendar. Based on ([calver](https://calver.org/)).
The supported convention is YYYY.MM.Patch with Patch a number not 0-padded starting to 1. (example: 2024.01.1).
Logic:
A commit with `feat` type activates an increment of the montg, otherwise all other types will activate an increment of the patch.
The year is automatically incremented at the end a year.
Then appends `.devN` where `N` is the distance between the current commit and the previous tag.
## Configuration
`foxy-project` can be configured thanks to its command line or configuration files (`foxy-project.toml` or `pyproject.toml`).
Configurations files are automatically looked up in the project's folder but custom path can always to passed to the command line.
Configurations from different sources are considered with an defined order.
Commande line options overrides configurations from `foxy-project.toml` which overrides configurations from `pyproject.toml`.
### Python project
`pyproject.toml` is supported and is the recommanded way to configure python projects.
### Hatch
[Hatch](https://github.com/pypa/hatch) is supported out of the box thanks to [hatch-vcs](https://github.com/ofek/hatch-vcs).
Python projet using other project management tool can use `foxy-project` directly.
Ensure `hatch-vcs` and `foxy-project` are defined within the `build-system.requires` field in your `pyproject.toml` file.
All other options supported by `hatch-vcs` can be used. More information can be found in their documentation.
Usure to run `hatch version` instead of `foxy-project version` to avoid conflicts.
Only the version management is integrated into Hatch which will generate the good version at build time.
Changelog generation can be configured into a `tool.foxy-project.changelog` section.
If no title and description are provided for the changelog the one from `project` configuration are taken.
```toml
[build-system]
requires = ["hatchling", "hatch-vcs", "foxy-project"]
build-backend = "hatchling.build"
[tool.hatch.version]
source = "vcs"
[tool.hatch.version.raw-options]
version_scheme = "semver-conventional-commit-foxy"
local_scheme = "no-local-version"
[tool.foxy-project.changelog]
tag_pattern = "semver"
```
### Other projects
`foxy-project.toml` is the recommanded way.
The following configuration block can be added to the `foxy-project.toml` file.
```toml
[changelog]
tag_pattern = "semver"
[version]
local_scheme = "no-local-version"
```
### Available configurations
```toml
# Changelog configuration
[changelog]
# foxy-project.toml
[tool.foxy-project.changelog]
# pyproject.toml
gitlab=false
github=true
title="Changelog"
description="description"
output="CHANGELOG.md"
remote="origin"
latest_version=""
unreleased=false
template="compact"
diff_url=""
issue_url=""
issue_pattern=""
tag_pattern="semver"
tag_prefix=""
stdout=false
starting_commit=""
stopping_commit="HEAD"
# Version configuration
[version]
# foxy-project.toml
[tool.foxy-project.version]
# pyproject.toml
version_scheme="semver-conventional-commit-foxy"
# See <https://setuptools-scm.readthedocs.io/en/latest/extending#setuptools_scmlocal_scheme>
local_scheme="node-and-date"
version_file=""
version_file_template=""
relative_to=""
tag_regex=""
parentdir_prefix_version=""
fallback_version=""
```
## Github actions
This repository is providing two composite actions to help automate release on Github actions:
- `setup-foxy-project` which set up the lastest version of foxy-project and add the command-line tools to the PATH.
- `generate-changelog` which generate the changelog and commit it on a branch.
- `create-release` which create a tag and the github release of a new version.
You can look at the workflows ([prepare-release](https://github.com/LeMimit/foxy-project/blob/7056bde43b0f0b7ce1d315e51225a0394352a8cf/.github/workflows/prepare-release.yml) and [create-release](https://github.com/LeMimit/foxy-project/blob/7056bde43b0f0b7ce1d315e51225a0394352a8cf/.github/workflows/create-release.yml)) of this project to see how to use them.
The advantage of this process is that it does not interfere with the protection of the default branch and no personal PAT needs to be created.
> [!NOTE]
> You need to allow workflows to create pull request in the settings of the repository.
## Command line interface
You can list the command line options by running `foxy-project --help`:
```console
Usage: foxy-project [OPTIONS] COMMAND [ARGS]...
Options:
--version Show the version and exit.
--help Show this message and exit.
Commands:
changelog Generate a changelog based on the commit history.
version View project's version based on the commit history.
```
### foxy-project changelog
You can list the options of `foxy-project changelog` by running `foxy-project changelog --help`:
```console
Usage: foxy-project changelog [OPTIONS]
Generate a changelog based on the commit history.
Options:
-c, --config PATH path to 'pyproject.toml' with foxy-project config
or 'foxy-project.toml' , default: looked up in
the current or parent directories
--gitlab Set Gitlab Pattern Generation.
--github Set GitHub Pattern Generation.
-p, --path-repo PATH Path to the repository's root directory [Default:
.]
-t, --title TEXT The changelog's title [Default: Changelog]
-d, --description TEXT Your project's description
-o, --output PATH The place to save the generated changelog
[Default: CHANGELOG.md]
-r, --remote TEXT Specify git remote to use for links
-v, --latest-version TEXT use specified version as latest release
-u, --unreleased Include section for unreleased changes
--template TEXT specify template to use [compact, lastrelease] or
a path to a custom template, default: compact
--diff-url TEXT override url for compares, use {current} and
{previous} for tags
--issue-url TEXT Override url for issues, use {id} for issue id
--issue-pattern TEXT Override regex pattern for issues in commit
messages. Should contain two groups, original
match and ID used by issue-url.
--tag-pattern TEXT Specify regex pattern for version tags [semver,
calendar, custom-regex]. A custom regex
containing one group named 'version' can be
specified.
--tag-prefix TEXT prefix used in version tags, default: ""
--stdout
--starting-commit TEXT Starting commit to use for changelog generation
--stopping-commit TEXT Stopping commit to use for changelog generation
--debug set logging level to DEBUG
--help Show this message and exit.
```
### foxy-project version
You can list the options of `foxy-project version` by running `foxy-project version --help`:
```console
Usage: foxy-project version [OPTIONS]
View project's version based on the commit history.
Options:
-c, --config PATH path to 'pyproject.toml' with foxy-project
config or 'foxy-project.toml' , default:
looked up in the current or parent
directories
-p, --path-repo PATH Path to the repository's root directory
[Default: .]
--version-scheme TEXT Configures how the local version number is
constructed;either an entrypoint name or a
callable. [Default: semver-conventional-
commit-foxy]
--local-scheme TEXT Configures how the local version number is
constructed;either an entrypoint name or a
callable. [Default: node-and-date]
--version-file PATH A path to a file that gets replaced with a
file containing the current version.
--version-file-template TEXT A new-style format string that is given the
currentversion as the version keyword
argument for formatting.
--relative-to PATH A file/directory from which the root can be
resolved.
--tag-regex TEXT A Python regex string to extract the version
part from any SCM tag.The regex needs to
contain either a single match group, or a
group named version,that captures the actual
version information.
--parentdir-prefix-version TEXT
If the normal methods for detecting the
version (SCM version, sdist metadata)
fail,and the parent directory name starts
with parentdir_prefix_version,then this
prefix is stripped and the rest of the
parent directory nameis matched with
tag_regex to get a version string.
--fallback-version TEXT A version string that will be used if no
other method for detecting the version
worked(e.g., when using a tarball with no
metadata).
--next Use the next possible version instead of the
current one.
--no-print Deactivate the print of the version.
--no-version-file Deactivate the generation of the version
file.
--debug set logging level to DEBUG
--help Show this message and exit.
```
Raw data
{
"_id": null,
"home_page": "",
"name": "foxy-project",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": "",
"keywords": "changelog,git",
"author": "",
"author_email": "Michael F Bryan <michaelfbryan@gmail.com>, Ken Mijime <kenaco666@gmail.com>, Fabien Hermitte <email@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/a5/b1/78d0c693af54b1c8db9a04501c86815e78102156f84492083803db7b3fd3/foxy_project-2.4.1.tar.gz",
"platform": null,
"description": "# \ud83e\udd8a Foxy project\n\n> [!IMPORTANT]\n> This repository is a fork of [auto-changelog](https://github.com/KeNaCo/auto-changelog).\n> I decided to do it because auto-changelog is not maintained anymore and I need some changes for my personal usage.\n> I will publish these changes for everyone to use but I do not promise to answer to feature request and bug fixes.\n>\n> **Sadly I do not have time to provide steps to contribute and not everything will be tested.**\n\n| | |\n| --- | --- |\n| Package | [](https://pypi.org/project/foxy-project/) [](https://pypi.org/project/foxy-project/) [](https://pypi.org/project/foxy-project/) |\n| Meta | [](https://github.com/pypa/hatch) [](https://github.com/astral-sh/ruff) [](https://github.com/python/mypy) [](https://spdx.org/licenses/) |\n\nA tool which generates a changelog and manage version for any git repository using [`conventional commits`](https://www.conventionalcommits.org/en/v1.0.0/) specification.\n\n- [Installation](#installation)\n- [Changelog generation](#changelog-generation)\n - [Add to an existing changelog](#add-to-an-existing-changelog)\n- [Version management](#version-management)\n - [pep440-conventional-commit-foxy](#pep440-conventional-commit-foxy)\n - [semver-conventional-commit-foxy](#semver-conventional-commit-foxy)\n - [calendar-conventional-commit-foxy](#calendar-conventional-commit-foxy)\n- [Configuration](#configuration)\n - [Python project](#python-project)\n - [Hatch](#hatch)\n - [Other projects](#other-projects)\n - [Available configurations](#available-configurations)\n- [Github actions](#github-actions)\n- [Command line interface](#command-line-interface)\n - [foxy-project changelog](#foxy-project-changelog)\n - [foxy-project version](#foxy-project-version)\n\n## Installation\n\nIt is recommanded to install this tool with [`pipx`](https://github.com/pypa/pipx) to install it in a isolated environments:\n\n```console\npipx install foxy-project\n```\n\n## Changelog generation\n\nRunnning the following command in the working environment will generate the project's changelog according to its commit history.\n\n```console\nfoxy-project changelog\n```\n\n### Add to an existing changelog\n\nIf you\u2019d like to keep an existing changelog below your generated one, just add `<!-- foxy-changelog-above -->` to your current changelog.\nThe generated changelog will be added above this token, and anything below will remain.\n\n> [!TIP]\n> This is quite useful when changing the tag pattern (e.g. from semver to calendar) used to version a project or to help keeping an old manually generated changelog when integrated conventional commit to a project.\n\n## Version management\n\n`foxy-project` is providing support to automatically generate the version of your python project according to its commit history.\n\nThe management is based on [setuptools_scm](https://github.com/pypa/setuptools_scm) and [conventional commit](https://www.conventionalcommits.org/en/v1.0.0/).\n\nAs defined in the conventional commit specification:\n\n>- The type `feat` MUST be used when a commit adds a new feature to your application or library.\n>- The type `fix` MUST be used when a commit represents a bug fix for your application.\n\nRunnning the following command in the working environment will print the project's version the according to its commit history.\n\n```console\nfoxy-project version\n```\n\n> [!TIP]\n> It is also possible to generate a file with the generated version. This behavior is deactivated by default.\n>\n> Use the `version_file` and `version_file_template` option to configure the generation.\n> Embedded templates for `.py` and `.txt` are available. A custom template needs to be provided for other type of file.\n\n`foxy-project` is providing three version schemas which control how the version is incremented.\n\n### pep440-conventional-commit-foxy\n\nBased on [PEP440](https://peps.python.org/pep-0440/). Selected by default.\n\nLogic:\n\nA commit with `feat` type activates an increment of the minor, otherwise all other types will activate an increment of the patch.\nThen appends `.devN` where `N` is the distance between the current commit and the previous tag.\n\n> [!WARNING]\n> Breaking changes and pre-release is not supported yet.\n\n### semver-conventional-commit-foxy\n\nBased on [semver](https://semver.org/lang/fr/).\n\nLogic:\n\nA commit with `feat` type activates an increment of the minor, otherwise all other types will activate an increment of the patch.\nThen appends `-devN` where `N` is the distance between the current commit and the previous tag.\n\n> [!WARNING]\n> Breaking changes and pre-release with other name than `dev` is not supported yet.\n\n### calendar-conventional-commit-foxy\n\nTo manage version based on the calendar. Based on ([calver](https://calver.org/)).\nThe supported convention is YYYY.MM.Patch with Patch a number not 0-padded starting to 1. (example: 2024.01.1).\n\nLogic:\n\nA commit with `feat` type activates an increment of the montg, otherwise all other types will activate an increment of the patch.\nThe year is automatically incremented at the end a year.\nThen appends `.devN` where `N` is the distance between the current commit and the previous tag.\n\n## Configuration\n\n`foxy-project` can be configured thanks to its command line or configuration files (`foxy-project.toml` or `pyproject.toml`).\n\nConfigurations files are automatically looked up in the project's folder but custom path can always to passed to the command line.\n\nConfigurations from different sources are considered with an defined order.\nCommande line options overrides configurations from `foxy-project.toml` which overrides configurations from `pyproject.toml`.\n\n### Python project\n\n`pyproject.toml` is supported and is the recommanded way to configure python projects.\n\n### Hatch\n\n[Hatch](https://github.com/pypa/hatch) is supported out of the box thanks to [hatch-vcs](https://github.com/ofek/hatch-vcs).\nPython projet using other project management tool can use `foxy-project` directly.\n\nEnsure `hatch-vcs` and `foxy-project` are defined within the `build-system.requires` field in your `pyproject.toml` file.\nAll other options supported by `hatch-vcs` can be used. More information can be found in their documentation.\n\nUsure to run `hatch version` instead of `foxy-project version` to avoid conflicts.\n\nOnly the version management is integrated into Hatch which will generate the good version at build time.\n\nChangelog generation can be configured into a `tool.foxy-project.changelog` section.\nIf no title and description are provided for the changelog the one from `project` configuration are taken.\n\n```toml\n[build-system]\nrequires = [\"hatchling\", \"hatch-vcs\", \"foxy-project\"]\nbuild-backend = \"hatchling.build\"\n\n[tool.hatch.version]\nsource = \"vcs\"\n\n[tool.hatch.version.raw-options]\nversion_scheme = \"semver-conventional-commit-foxy\"\nlocal_scheme = \"no-local-version\"\n\n[tool.foxy-project.changelog]\ntag_pattern = \"semver\"\n```\n\n### Other projects\n\n`foxy-project.toml` is the recommanded way.\n\nThe following configuration block can be added to the `foxy-project.toml` file.\n\n```toml\n[changelog]\ntag_pattern = \"semver\"\n\n[version]\nlocal_scheme = \"no-local-version\"\n```\n\n### Available configurations\n\n```toml\n\n# Changelog configuration\n\n[changelog]\n# foxy-project.toml\n\n[tool.foxy-project.changelog]\n# pyproject.toml\ngitlab=false\ngithub=true\ntitle=\"Changelog\"\ndescription=\"description\"\noutput=\"CHANGELOG.md\"\nremote=\"origin\"\nlatest_version=\"\"\nunreleased=false\ntemplate=\"compact\"\ndiff_url=\"\"\nissue_url=\"\"\nissue_pattern=\"\"\ntag_pattern=\"semver\"\ntag_prefix=\"\"\nstdout=false\nstarting_commit=\"\"\nstopping_commit=\"HEAD\"\n\n# Version configuration\n\n[version]\n# foxy-project.toml\n\n\n[tool.foxy-project.version]\n# pyproject.toml\nversion_scheme=\"semver-conventional-commit-foxy\"\n# See <https://setuptools-scm.readthedocs.io/en/latest/extending#setuptools_scmlocal_scheme>\nlocal_scheme=\"node-and-date\"\nversion_file=\"\"\nversion_file_template=\"\"\nrelative_to=\"\"\ntag_regex=\"\"\nparentdir_prefix_version=\"\"\nfallback_version=\"\"\n```\n\n## Github actions\n\nThis repository is providing two composite actions to help automate release on Github actions:\n\n- `setup-foxy-project` which set up the lastest version of foxy-project and add the command-line tools to the PATH.\n- `generate-changelog` which generate the changelog and commit it on a branch.\n- `create-release` which create a tag and the github release of a new version.\n\nYou can look at the workflows ([prepare-release](https://github.com/LeMimit/foxy-project/blob/7056bde43b0f0b7ce1d315e51225a0394352a8cf/.github/workflows/prepare-release.yml) and [create-release](https://github.com/LeMimit/foxy-project/blob/7056bde43b0f0b7ce1d315e51225a0394352a8cf/.github/workflows/create-release.yml)) of this project to see how to use them.\n\nThe advantage of this process is that it does not interfere with the protection of the default branch and no personal PAT needs to be created.\n\n> [!NOTE]\n> You need to allow workflows to create pull request in the settings of the repository.\n\n## Command line interface\n\nYou can list the command line options by running `foxy-project --help`:\n\n```console\nUsage: foxy-project [OPTIONS] COMMAND [ARGS]...\n\nOptions:\n --version Show the version and exit.\n --help Show this message and exit.\n\nCommands:\n changelog Generate a changelog based on the commit history.\n version View project's version based on the commit history.\n```\n\n### foxy-project changelog\n\nYou can list the options of `foxy-project changelog` by running `foxy-project changelog --help`:\n\n```console\nUsage: foxy-project changelog [OPTIONS]\n\n Generate a changelog based on the commit history.\n\nOptions:\n -c, --config PATH path to 'pyproject.toml' with foxy-project config\n or 'foxy-project.toml' , default: looked up in\n the current or parent directories\n --gitlab Set Gitlab Pattern Generation.\n --github Set GitHub Pattern Generation.\n -p, --path-repo PATH Path to the repository's root directory [Default:\n .]\n -t, --title TEXT The changelog's title [Default: Changelog]\n -d, --description TEXT Your project's description\n -o, --output PATH The place to save the generated changelog\n [Default: CHANGELOG.md]\n -r, --remote TEXT Specify git remote to use for links\n -v, --latest-version TEXT use specified version as latest release\n -u, --unreleased Include section for unreleased changes\n --template TEXT specify template to use [compact, lastrelease] or\n a path to a custom template, default: compact\n --diff-url TEXT override url for compares, use {current} and\n {previous} for tags\n --issue-url TEXT Override url for issues, use {id} for issue id\n --issue-pattern TEXT Override regex pattern for issues in commit\n messages. Should contain two groups, original\n match and ID used by issue-url.\n --tag-pattern TEXT Specify regex pattern for version tags [semver,\n calendar, custom-regex]. A custom regex\n containing one group named 'version' can be\n specified.\n --tag-prefix TEXT prefix used in version tags, default: \"\"\n --stdout\n --starting-commit TEXT Starting commit to use for changelog generation\n --stopping-commit TEXT Stopping commit to use for changelog generation\n --debug set logging level to DEBUG\n --help Show this message and exit.\n```\n\n### foxy-project version\n\nYou can list the options of `foxy-project version` by running `foxy-project version --help`:\n\n```console\nUsage: foxy-project version [OPTIONS]\n\n View project's version based on the commit history.\n\nOptions:\n -c, --config PATH path to 'pyproject.toml' with foxy-project\n config or 'foxy-project.toml' , default:\n looked up in the current or parent\n directories\n -p, --path-repo PATH Path to the repository's root directory\n [Default: .]\n --version-scheme TEXT Configures how the local version number is\n constructed;either an entrypoint name or a\n callable. [Default: semver-conventional-\n commit-foxy]\n --local-scheme TEXT Configures how the local version number is\n constructed;either an entrypoint name or a\n callable. [Default: node-and-date]\n --version-file PATH A path to a file that gets replaced with a\n file containing the current version.\n --version-file-template TEXT A new-style format string that is given the\n currentversion as the version keyword\n argument for formatting.\n --relative-to PATH A file/directory from which the root can be\n resolved.\n --tag-regex TEXT A Python regex string to extract the version\n part from any SCM tag.The regex needs to\n contain either a single match group, or a\n group named version,that captures the actual\n version information.\n --parentdir-prefix-version TEXT\n If the normal methods for detecting the\n version (SCM version, sdist metadata)\n fail,and the parent directory name starts\n with parentdir_prefix_version,then this\n prefix is stripped and the rest of the\n parent directory nameis matched with\n tag_regex to get a version string.\n --fallback-version TEXT A version string that will be used if no\n other method for detecting the version\n worked(e.g., when using a tarball with no\n metadata).\n --next Use the next possible version instead of the\n current one.\n --no-print Deactivate the print of the version.\n --no-version-file Deactivate the generation of the version\n file.\n --debug set logging level to DEBUG\n --help Show this message and exit.\n```\n",
"bugtrack_url": null,
"license": "",
"summary": "A tool which generates a changelog and manage version for any git repository using conventional commits specification",
"version": "2.4.1",
"project_urls": {
"Documentation": "https://github.com/LeMimit/foxy-project#readme",
"Issues": "https://github.com/LeMimit/foxy-project/issues",
"Source": "https://github.com/LeMimit/foxy-project"
},
"split_keywords": [
"changelog",
"git"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "f9fe9243e9dbd65cebcb24330dd2dcb78b7aa3059bb3734f457e114363f53ed9",
"md5": "5369ccc0910e36d8e288ef0fea011deb",
"sha256": "50796592a39f0758555b595976416c0748d744bdb2b987fcb7c946fb4975482e"
},
"downloads": -1,
"filename": "foxy_project-2.4.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "5369ccc0910e36d8e288ef0fea011deb",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 30702,
"upload_time": "2024-02-11T09:33:23",
"upload_time_iso_8601": "2024-02-11T09:33:23.302592Z",
"url": "https://files.pythonhosted.org/packages/f9/fe/9243e9dbd65cebcb24330dd2dcb78b7aa3059bb3734f457e114363f53ed9/foxy_project-2.4.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "a5b178d0c693af54b1c8db9a04501c86815e78102156f84492083803db7b3fd3",
"md5": "dec49372f583cb32e6f2389b38ad20fc",
"sha256": "26ce83928dc42035dc0ea4965ec2816e6734cad6c41e756ad089a0996decc064"
},
"downloads": -1,
"filename": "foxy_project-2.4.1.tar.gz",
"has_sig": false,
"md5_digest": "dec49372f583cb32e6f2389b38ad20fc",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 40172,
"upload_time": "2024-02-11T09:33:24",
"upload_time_iso_8601": "2024-02-11T09:33:24.957142Z",
"url": "https://files.pythonhosted.org/packages/a5/b1/78d0c693af54b1c8db9a04501c86815e78102156f84492083803db7b3fd3/foxy_project-2.4.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-02-11 09:33:24",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "LeMimit",
"github_project": "foxy-project#readme",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "foxy-project"
}
