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 5 of 40

9.7.2

Not secure
Bug Fixes

- Enable user configuration of `build_command` env vars
([925](https://github.com/python-semantic-release/python-semantic-release/pull/925),
[`6b5b271`](https://github.com/python-semantic-release/python-semantic-release/commit/6b5b271453874b982fbf2827ec1f6be6db1c2cc7))

- test(version): add test of user defined env variables in build command

ref: 922

- fix(version): enable user config of `build_command` env variables

Resolves: 922

- docs(configuration): document `build_command_env` configuration option

Documentation

- **configuration**: Clarify TOC & alphabetize configuration descriptions
([`19add16`](https://github.com/python-semantic-release/python-semantic-release/commit/19add16dcfdfdb812efafe2d492a933d0856df1d))

- **configuration**: Clarify TOC & standardize heading links
([`3a41995`](https://github.com/python-semantic-release/python-semantic-release/commit/3a4199542d0ea4dbf88fa35e11bec41d0c27dd17))

9.7.1

Not secure
Bug Fixes

- **gha**: Fix missing `git_committer_*` definition in action
([919](https://github.com/python-semantic-release/python-semantic-release/pull/919),
[`ccef9d8`](https://github.com/python-semantic-release/python-semantic-release/commit/ccef9d8521be12c0640369b3c3a80b81a7832662))

Resolves: 918

9.7.0

Not secure
Bug Fixes

- **gha**: Add missing `tag` option to GitHub Action definition
([908](https://github.com/python-semantic-release/python-semantic-release/pull/908),
[`6b24288`](https://github.com/python-semantic-release/python-semantic-release/commit/6b24288a96302cd6982260e46fad128ec4940da9))

Resolves: 906

Documentation

- **configuration**: Add description of build command available env variables
([`c882dc6`](https://github.com/python-semantic-release/python-semantic-release/commit/c882dc62b860b2aeaa925c21d1524f4ae25ef567))

Features

- **version-cmd**: Pass `NEW_VERSION` & useful env vars to build command
([`ee6b246`](https://github.com/python-semantic-release/python-semantic-release/commit/ee6b246df3bb211ab49c8bce075a4c3f6a68ed77))

9.6.0

Not secure
Bug Fixes

- Correct version `--prerelease` use & enable `--as-prerelease`
([647](https://github.com/python-semantic-release/python-semantic-release/pull/647),
[`2acb5ac`](https://github.com/python-semantic-release/python-semantic-release/commit/2acb5ac35ae79d7ae25ca9a03fb5c6a4a68b3673))

* test(version): add validation of `--as-prerelease` and `--prerelease opts`

* fix(version-cmd): correct `--prerelease` use

Prior to this change, `--prerelease` performed the role of converting whichever forced version into
a prerelease version declaration, which was an unintentional breaking change to the CLI compared
to v7.

`--prerelease` now forces the next version to increment the prerelease revision, which makes it
consistent with `--patch`, `--minor` and `--major`. Temporarily disabled the ability to force a
prerelease.

Resolves: 639

* feat(version-cmd): add `--as-prerelease` option to force the next version to be a prerelease

Prior to this change, `--prerelease` performed the role that `--as-prerelease` now does, which was
an unintentional breaking change to the CLI compared to v7.

`--prerelease` is used to force the next version to increment the prerelease revision, which makes
it consistent with `--patch`, `--minor` and `--major`, while `--as-prerelease` forces for the next
version to be converted to a prerelease version type before it is applied to the project
regardless of the bump level.

* docs(commands): update version command options definition about prereleases

---------

Co-authored-by: codejedi365 <codejedi365gmail.com>

- **parser-custom**: Gracefully handle custom parser import errors
([`67f6038`](https://github.com/python-semantic-release/python-semantic-release/commit/67f60389e3f6e93443ea108c0e1b4d30126b8e06))

Features

- Changelog filters are specialized per vcs type
([890](https://github.com/python-semantic-release/python-semantic-release/pull/890),
[`76ed593`](https://github.com/python-semantic-release/python-semantic-release/commit/76ed593ea33c851005994f0d1a6a33cc890fb908))

* test(github): sync pr url expectation with GitHub api documentation

* fix(github): correct changelog filter for pull request urls

* refactor(hvcs-base): change to an abstract class & simplify interface

* refactor(remote-hvcs-base): extend the base abstract class with common remote base class

* refactor(github): adapt to new abstract base class

* refactor(gitea): adapt to new abstract base class

* refactor(gitlab): adapt to new abstract base class

* refactor(bitbucket): adapt to new abstract base class

* refactor(cmds): prevent hvcs from executing if not remote hosted vcs

* feat(changelog): changelog filters are hvcs focused

* test(hvcs): add validation for issue_url generation

* feat(changelog-github): add issue url filter to changelog context

* feat(changelog-gitea): add issue url filter to changelog context

* refactor(cmd-version): consolidate asset uploads with release creation

* style: resolve ruff errors

* feat(changelog-context): add flag to jinja env for which hvcs is available

* test(changelog-context): demonstrate per hvcs filters upon render

* docs(changelog-context): explain new hvcs specific context filters

* refactor(config): adjust default token resolution w/ subclasses

9.5.0

Not secure
Build System

- **deps**: Bump ruff from 0.3.5 to 0.3.7
([894](https://github.com/python-semantic-release/python-semantic-release/pull/894),
[`6bf2849`](https://github.com/python-semantic-release/python-semantic-release/commit/6bf28496d8631ada9009aec5f1000f68b7f7ee16))

Features

- Extend support to on-prem GitHub Enterprise Server
([896](https://github.com/python-semantic-release/python-semantic-release/pull/896),
[`4fcb737`](https://github.com/python-semantic-release/python-semantic-release/commit/4fcb737958d95d1a3be24db7427e137b46f5075f))

* test(github): adjust init test to match the Enterprise Server api url

* feat(github): extend support to on-prem GitHub Enterprise Server

Resolves: 895

9.4.2

Not secure
Bug Fixes

- **hvcs**: Allow insecure http connections if configured
([886](https://github.com/python-semantic-release/python-semantic-release/pull/886),
[`db13438`](https://github.com/python-semantic-release/python-semantic-release/commit/db1343890f7e0644bc8457f995f2bd62087513d3))

* fix(gitlab): allow insecure http connections if configured

* test(hvcs-gitlab): fix tests for clarity & insecure urls

* test(conftest): refactor netrc generation into common fixture

* refactor(hvcsbase): remove extrenous non-common functionality

* fix(gitea): allow insecure http connections if configured

* test(hvcs-gitea): fix tests for clarity & insecure urls

* refactor(gitlab): adjust init function signature

* fix(github): allow insecure http connections if configured

* test(hvcs-github): fix tests for clarity & insecure urls

* fix(bitbucket): allow insecure http connections if configured

* test(hvcs-bitbucket): fix tests for clarity & insecure urls

* fix(config): add flag to allow insecure connections

* fix(version-cmd): handle HTTP exceptions more gracefully

* style(hvcs): resolve typing issues & mimetype executions

* test(cli-config): adapt default token test for env resolution

* test(changelog-cmd): isolate env & correct the expected api url

* test(fixtures): adapt repo builder for new hvcs init() signature

* style: update syntax for 3.8 compatiblity & formatting

* docs(configuration): update `remote` settings section with missing values

Resolves: 868

* style(docs): improve configuration & api readability

- **hvcs**: Prevent double url schemes urls in changelog
([676](https://github.com/python-semantic-release/python-semantic-release/pull/676),
[`5cfdb24`](https://github.com/python-semantic-release/python-semantic-release/commit/5cfdb248c003a2d2be5fe65fb61d41b0d4c45db5))

* fix(hvcs): prevent double protocol scheme urls in changelogs

Due to a typo and conditional stripping of the url scheme the hvcs_domain and hvcs_api_domain values
would contain protocol schemes when a user specified one but the defaults would not. It would
cause the api_url and remote_url to end up as "https://https://domain.com"

* fix(bitbucket): correct url parsing & prevent double url schemes

* fix(gitea): correct url parsing & prevent double url schemes

* fix(github): correct url parsing & prevent double url schemes

* fix(gitlab): correct url parsing & prevent double url schemes

* test(hvcs): ensure api domains are derived correctly

---------

Co-authored-by: codejedi365 <codejedi365gmail.com>

Build System

- **deps**: Update rich requirement from ~=12.5 to ~=13.0
([877](https://github.com/python-semantic-release/python-semantic-release/pull/877),
[`4a22a8c`](https://github.com/python-semantic-release/python-semantic-release/commit/4a22a8c1a69bcf7b1ddd6db56e6883c617a892b3))

Updates the requirements on [rich](https://github.com/Textualize/rich) to permit the latest version.
- [Release notes](https://github.com/Textualize/rich/releases) -
[Changelog](https://github.com/Textualize/rich/blob/master/CHANGELOG.md)

Resolves: 888

Signed-off-by: dependabot[bot] <supportgithub.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]users.noreply.github.com>

Page 5 of 40

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.