[pull] master from python-semantic-release:master #98
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
* 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
) * 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. Resolves: #639 * docs(commands): update version command options definition about prereleases --------- Co-authored-by: codejedi365 <codejedi365@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )