Skip to content

[pull] master from python-semantic-release:master#175

Open
pull[bot] wants to merge 344 commits intoFoundryAI:masterfrom
python-semantic-release:master
Open

[pull] master from python-semantic-release:master#175
pull[bot] wants to merge 344 commits intoFoundryAI:masterfrom
python-semantic-release:master

Conversation

@pull
Copy link

@pull pull bot commented Dec 2, 2024

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added ⤵️ pull merge-conflict Resolve conflicts manually labels Dec 2, 2024
dependabot bot and others added 28 commits February 17, 2025 01:31
…ript (#1199)

Adds support for default implementation of `uvx` which matches script name with
package name.

Resolves: #1195

* test(cli): add entrypoint script validation
…isions (#1200)

Resolves: #1201

* docs(github-actions): update example workflow to handle rapid merges

* ci(release): reduce extra steps in deploy job

* ci(validate): simplify build job to use psr action

* ci(release): reduce extra steps in release job
Automatically generated by python-semantic-release
…1228)

The primary change from `v4` to `v5` in this dependency was the removal of
identified support for `Python 3.8`.  Since we still support `Python 3.8`,
then we need to maintain the flexibility for 3.8 package managers to install
`v4` while allowing more modern projects to use the new features of `v5`
along side `python-semantic-release`.

Co-authored-by: Neil McDonald <nmcdonald@gitlab.com>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ng actions (#1229)

Co-authored-by: codejedi365 <codejedi365@gmail.com>
…v77`, & `v78` (#1225)

This expansion maintains support for python 3.8 while accepting the new features of
setuptools with more modern python versions.

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…80` (#1237)

Co-authored-by: codejedi365 <codejedi365@users.noreply.github.com>
* chore(project-config): remove the source code version stamp during release
… letters (#1239)

The change adjusts the url normalization computation to remove any
path prefix and only the path prefix even when letters are shared with
the rest of the url path.

Resolves: #1204

* test(hvcs-bitbucket): add validation for self hosted server commit url
Automatically generated by python-semantic-release
click 8.2 has a breaking change in the test suite where it removes
a parameter from the cli runner. There is additional deprecation
warnings included as well so for now since it will break our tests
limit this to 8.1.0 only.
…ith double-equals (#1244)

* test(stamp-version): add test case for stamping a `requirements.txt` file with double-equals

* docs(configuration): update `version_variables` section to include double-equals operand support
…n script

Prevents the malicious execution of arbitrary code when a command injection is
defined in the action yaml as part of the action parameter specification. Low
impact exploitation if proper least privilege is implemented and pull request
code is reviewed before merging to a release branch.

BREAKING CHANGE: The `root_options` action input parameter has been removed
because it created a command injection vulernability for arbitrary code to
execute within the container context of the GitHub action if a command injection
code was provided as part of the `root_options` parameter string. To eliminate
the vulnerability, each relevant option that can be provided to `semantic-release`
has been individually added as its own parameter and will be processed individually
to prevent command injection. Please review our `Github Actions Configuration`__
page on the Python Semantic Release Documentation website to review the newly available
configuration options that replace the `root_options` parameter.

__ https://python-semantic-release.readthedocs.io/en/stable/automatic-releases/github-actions.html
codejedi365 and others added 30 commits November 9, 2025 22:49
…anch tracking (#1369)

* test(cmd-version): add CI simulated upstream verification of non-tracked branch

* test(gitproject): update unit tests to exercise non-tracking branch derivation errors
Automatically generated by python-semantic-release
…s made (#1370)

* test(cmd-version): add e2e test case to check for no upstream check when no version commit
Automatically generated by python-semantic-release
* chore(release): set `add_partial_tags` to true for PSR releases

* ci(release): remove job steps to create partial tags
…m action environment (#1389)

Install openssh-client in the slim container image

Resolves: #1376

* test(gh-action): add SSH signing test case

  Add test to verify SSH signing key configuration in the GitHub Action.
  The test generates an SSH key pair and validates that ssh-agent and
  ssh-add commands execute successfully when SSH signing keys are provided.
…m verification (#1388)

This change updates verify_upstream_unchanged to accept and use an authenticated
remote_url parameter when fetching from the remote, mirroring the approach used
for git push operations. This resolves authentication issues when verifying upstream
state in repositories that require token authentication for fetch operations.

Resolves: #1373

* test(gitproject): add another unit test for verify upstream unchanged with authed url
Automatically generated by python-semantic-release
…fault emoji parser (#1410)

* test(parser-emoji): add unit tests for no-release triggering emoji commits
…1397)

Resolves: #1395

* fix(github): fix bubble up errors of asset uploads for GitHub

* test(cmd-publish): add e2e test for handling GitHub authentication errors on upload

* test(github): add comprehensive error tests for `upload_dists()`
…-8 encoding (#1400)

Resolves: #702

* docs(cmd-config-generate): add Windows PowerShell specific `generate-config` usage example

* test(cmd-config-generate): adds UTF-8 encoding test for platform specific output
…s` (#1391)

Add support for entire file replacement when pattern is specified as `*`. This allows users to
configure version stamping for files that contain only a version number (e.g., VERSION files).

Implements: #1375

* docs(configuration): modify `version_variables` definition to include new file replacement

* test(cmd-version): add version stamp test for a version file

* test(version): add unit test for file declaration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

⤵️ pull merge-conflict Resolve conflicts manually

Projects

None yet

Development

Successfully merging this pull request may close these issues.