Miniver

Latest version: v0.8.0

Safety actively analyzes 613603 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

0.7.0

Added
- Allow distributions that place packages in a "src" directory
Changed
- Replace tool "install-miniver" with a tool "miniver" with a command "install"
Fixed
- Use "build_py" from setuptools, rather than distutils, which prevents a warning
being displayed when using more recent setuptools versions

0.6.0

Fixed
- Typos in generated files (comments only)
- Dedented template code produced by 'install-miniver' to make it copy-pasteable.


Making a miniver release
These instructions can also be used as a starting point for packages that use miniver.

Preflight checks

1. Verify that all issues/pull requests pertinent for this release are closed/merged
2. Verify that all changes are recorded in the changelog
3. Verify that any attribution files (e.g AUTHORS) are up to date
4. Verify that copyright notices are up to date
5. Verify that the builds are passing on `master`

Prepare the release

1. Restore the git repository to a pristine state: `git checkout master && git reset --hard HEAD && git clean -xd -f`
2. Create a *signed*, *annotated* release tag: `git tag -as vX.Y.Z -m 'version X.Y.Z'`
3. Create source and binary distributions: `python setup.py sdist bdist_wheel`
4. Create an empty commit to start development towards the next release: `git commit --allow-empty -m 'start development towards A.B.C'`
5. Create a *signed*, *annotated* pre-release tag: `git tag -as vA.B.C-dev -m 'work towards A.B.C'`

Publish the release
1. Push the new version and development tags: `git push upstream vX.Y.Z vA.B.C-dev`
2. Upload the distributions to PyPI: `twine upload dist/*`

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.