Package: ne-ver
ne-ver - Next VersionNe-ver again the manual hassle to release a next version.basic usageSetup an environment with the dependencies once, if you haven't done that yet.$ python -m venv .venv
$ source .venv/bin/activate
$ pip install ne-ver
$ never -h
usage: never [-h] [--settings | --no-settings] [-f SETTINGS_FILE] [-p PROJECT] {major,minor,patch}

Ne-ver again the manual hassle to release a next version

positional arguments:
  {major,minor,patch}

optional arguments:
  -h, --help            show this help message and exit
  --settings, --no-settings
                        whether to use a settings-file for your configuration, or provide the settings manually

required when using a settings-file for your configuration:
  -f SETTINGS_FILE, --settings-file SETTINGS_FILE
  -p PROJECT, --project PROJECT

Website: https://github.com/swesterveld/nextGitHub Personal Access TokenA GitHub Personal Access Token (PAT) is required to letnevercreate pull requests for you.
Make sure to generate a PAT inyour GitHub Developer Settings,
with at least the scoperepo-- for full control of private repositories -- selected.Add this token to the.envfile at the root of your virtualenv.
The.envfile should be based on the.env.examplefile in theexamplesdirectory.
Make sure to reload the virtualenv to activate the environment variable(s) defined in the.envfile.settingsCurrently, the--no-settingsflag doesn't work yet, so you should use a settings file.
The settings file should be JSON-formatted. Its contents should be like:{"projects":{"backend":{"path":"~/repos/some-repo-clone-of-backend-project","branches":{"release":"release/{version}","staging":"develop","production":"master"},"version_file":"VERSION"},"frontend":{"path":"/home/jdoe/repos/some-repo-clone-of-frontend-project","branches":{"release":"release/{version}","staging":"develop","production":"master"},"version_file":"VERSION","package_metadata":"package.json"}}}runAn example, to bump the version fromx.y.ztox.y.z+1for projectfrontenddefined inetc/never.config.json:never patch --settings -f etc/never.config.json -p frontendadvanced usage: auto mergeWhen you would like to automagically merge the release branch created byneveron GitHub, you should use a deploy key.
To create one, issue:ssh-keygen -t ed25519 -C "<comment>" -f <filename>Where the outputfile should be specified by<filename>, and-C "<comment>"is optional, and could contain any
comment that may be useful to help identify the key.This results in a key-pair, with its private part in<filename>and its public part in<filename>.pub.
In your repository settings (athttps://github.com///settings), you should use the contents of
those files to add a deploy key and a secret:The public part should be added to your repository as a deploy keywith write access.The private part should be added as a new repository secret calledNEVER_DEPLOY_KEY.Besides that, a GitHub Action that will use these this key-pair to automagically merge the release branch is required.
An example could be found at.github/workflows/merge-release.ymland should be copied to.github/workflows/in your
repository.developmentrun in development modeYou could benefit from the option torunsetuptoolsin development mode,
which allows you to modify the source code and have the changes take effect without you having to rebuild and reinstall:pip install  --editable .build Python packageAs a prerequisite for building a Python package you'll need a builder, such asPyPA build.
If you haven't got a builder yet, you can obtain it viapip install build.To invoke the builder:python -m buildrelease to PyPIpython -m twine upload --repository pypi dist/*dependenciesThis project has some dependencies mentioned in therequirements.txtfile.
Documentation of these Python packages could be found at:GitPythonpython-dotenvRequestsOther dependencies, from the Python Standard Library, are documented here:argparse