Python-semantic-release

Latest version: v9.15.2

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

Scan your dependencies

Page 30 of 40

4.5.1

Not secure
Bug Fixes

- **github**: Send token in request header
([`be9972a`](https://github.com/python-semantic-release/python-semantic-release/commit/be9972a7b1fb183f738fb31bd370adb30281e4d5))

Use an Authorization header instead of deprecated query parameter authorization.

Fixes relekang/python-semantic-release167

Documentation

- Add note about automatic releases in readme
([`e606e75`](https://github.com/python-semantic-release/python-semantic-release/commit/e606e7583a30167cf7679c6bcada2f9e768b3abe))

- Fix broken list in readme
([`7aa572b`](https://github.com/python-semantic-release/python-semantic-release/commit/7aa572b2a323ddbc69686309226395f40c52b469))

Fix the syntax of a broken bullet-point list in README.rst.

- Update readme and getting started docs
([`07b3208`](https://github.com/python-semantic-release/python-semantic-release/commit/07b3208ff64301e544c4fdcb48314e49078fc479))

4.5.0

Not secure
Bug Fixes

- Remove erroneous submodule
([`762bfda`](https://github.com/python-semantic-release/python-semantic-release/commit/762bfda728c266b8cd14671d8da9298fc99c63fb))

- **cli**: --noop flag works when before command
([`4fcc781`](https://github.com/python-semantic-release/python-semantic-release/commit/4fcc781d1a3f9235db552f0f4431c9f5e638d298))

The entry point of the app is changed from main() to entry(). Entry takes any arguments before
commands and moves them to after commands, then calls main()

Closes 73

Features

- **history**: Enable colon defined version
([`7837f50`](https://github.com/python-semantic-release/python-semantic-release/commit/7837f5036269328ef29996b9ea63cccd5a6bc2d5))

The get_current_version_by_config_file and the replace_version_string methods now check for both
variables defined as "variable= version" and "variable: version" This allows for using a yaml file
to store the version.

Closes 165

4.4.1

Bug Fixes

- Add quotes around twine arguments
([`46a83a9`](https://github.com/python-semantic-release/python-semantic-release/commit/46a83a94b17c09d8f686c3ae7b199d7fd0e0e5e5))

Fixes 163

4.4.0

Not secure
Bug Fixes

- **github**: Add check for GITHUB_ACTOR for git push
([162](https://github.com/python-semantic-release/python-semantic-release/pull/162),
[`c41e9bb`](https://github.com/python-semantic-release/python-semantic-release/commit/c41e9bb986d01b92d58419cbdc88489d630a11f1))

Features

- **parser**: Add support for exclamation point for breaking changes
([`a4f8a10`](https://github.com/python-semantic-release/python-semantic-release/commit/a4f8a10afcc358a8fbef83be2041129480350be2))

According to the documentation for conventional commits, breaking changes can be described using
exclamation points, just before the colon between type/scope and subject. In that case, the
breaking change footer is optional, and the subject is used as description of the breaking change.
If the footer exists, it is used for the description.

Fixes 156

- **parser**: Make BREAKING-CHANGE synonymous with BREAKING CHANGE
([`beedccf`](https://github.com/python-semantic-release/python-semantic-release/commit/beedccfddfb360aeebef595342ee980446012ec7))

According to point 16 in the conventional commit specification, this should be implemented. They
especially mention the footer, but I kept the body for backwards compatibility. This should
probably be removed one day. The regex is in the helpers to make it easier to re-use, but I didn't
updated parser_tag since it looks like a legacy parser.

4.3.4

Not secure
Bug Fixes

- Fallback to whole log if correct tag is not available
([157](https://github.com/python-semantic-release/python-semantic-release/pull/157),
[`252bffd`](https://github.com/python-semantic-release/python-semantic-release/commit/252bffd3be7b6dfcfdb384d24cb1cd83d990fc9a))

The method getting all commits to consider for the release will now test whether the version in
input is a valid reference. If it is not, it will consider the whole log for the repository.

evaluate_version_bump will still consider a message starting with the version number as a breaking
condition to stop analyzing.

Fixes 51

4.3.3

Not secure
Bug Fixes

- Set version of click to >=2.0,<8.0.
([155](https://github.com/python-semantic-release/python-semantic-release/pull/155),
[`f07c7f6`](https://github.com/python-semantic-release/python-semantic-release/commit/f07c7f653be1c018e443f071d9a196d9293e9521))

* fix: Upgrade to click 7.0.

Fixes 117

* fix: Instead of requiring click 7.0, looks like all tests will pass with at least 2.0.

* Upstream is at ~=7.0, so let's set the range to less than 8.0.

* The string template has no variables, so remove the call to .format()

Page 30 of 40

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.