forked from python-semantic-release/python-semantic-release
-
Notifications
You must be signed in to change notification settings - Fork 0
[pull] master from python-semantic-release:master #175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
pull
wants to merge
117
commits into
FoundryAI:master
Choose a base branch
from
python-semantic-release:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or 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
…rsion type sections
…ns (#1104) * test(fixtures): refactor repo build helpers for construction steps * test(fixtures): refactor github flow default release repo for construction steps * test(fixtures): refactor github flow feature release repo for construction steps * test(fixtures): refactor initial commit repo for construction steps * test(fixtures): refactor trunk-only unreleased repo for construction steps * test(fixtures): refactor trunk-only repo w/ tags for construction steps * test(fixtures): refactor trunk-only repo w/ prereleases for construction steps * test(fixtures): add git fast forward merge action to repo builder * test(fixtures): refactor gitflow repo w/ 2 release channels for construction steps * test(fixtures): refactor gitflow repo w/ 3 release channels for construction steps * test(fixtures): add a gitflow repo w/ 4 release channels * test(fixtures): add a gitflow repo w/ a single release channel * test(e2e): refactor test cases to match repo construction step implementation * test(release-history): refactor unit tests to handle repo construction steps * build(deps-test): add `flatdict@4` to easily read `pyproject.toml` settings in test
* build(deps-dev): add missing type stubs for pyyaml * style(tests): fix or consciously ignore type errors throughout test code * chore(mypy): adjust rule configuration for mypy * chore(tox): adjust mypy call to type check entire repo in tox configuration * ci(validate-wkflow): adjust lint job to call mypy across entire repository
…pported (#1107) * test(release-notes): adjust test case to include a version compare link * test(cmd-changelog): add test to ensure multiple variants of release notes are published
…changelog (#1108) This adds an attribute to the ParsedCommit object that allows custom parsers to set to false if it is desired to ignore the commit completely from entry into the changelog. Resolves: #778 * test(parser-custom): add test w/ parser that toggles if a parsed commit is included in changelog
…nge sections (#1111) * test(fixtures): force non-alphabetical release history to validate template sorting * test(default-changelog): update unit test to enforce sorting of commit desc in version sections * test(release-notes): update unit test to enforce sorting of commit desc in version sections * feat(changelog-md): alphabetize commit summaries & scopes in markdown changelog template * feat(changelog-rst): alphabetize commit summaries & scopes in ReStructuredText template
…ction (#1110) Resolves: #244 * test(fixtures): update repo changelog generator to add breaking descriptions * test(default-changelog): add unit tests to demonstrate breaking change descriptions * test(release-notes): add unit tests to demonstrate breaking change descriptions * feat(changelog-md): add a breaking changes section to default Markdown template Resolves: #244 * feat(changelog-rst): add a breaking changes section to default reStructuredText template Resolves: #244 * feat(changelog-md): alphabetize breaking change descriptions in markdown changelog template * feat(changelog-rst): alphabetize breaking change descriptions in ReStructuredText template
…1109) * refactor(parsers): add parser option validation to commit parsing * docs(api-parsers): add option documentation to parser options * feat(parsers): add `other_allowed_tags` option for commit parser options * feat(parser-custom): enable custom parsers to identify linked issues on a commit * test(parser-angular): add unit tests to verify parsing of issue numbers * test(parser-emoji): add unit tests to verify parsing of issue numbers * test(parser-scipy): add unit tests to verify parsing of issue numbers * fix(util): prevent git footers from being collapsed during parse * feat(parser-angular): automatically parse angular issue footers from commit messages * feat(parser-emoji): parse issue reference footers from commit messages * docs(commit-parsing): improve & expand commit parsing w/ parser descriptions * docs(changelog-templates): update examples using new `commit.linked_issues` attribute * chore(docs): update documentation configuration for team publishing
…1113) * ci(deps): bump `python-semantic-release/publish-action` action from 9.14.0 to 9.15.0 * ci(deps): bump `mikepenz/action-junit-report` action from 5.0.0 to 5.1.0
… than text sorted
… single newline (#1118)
…& git flow merges (#1120) * refactor: define a custom logging level of silly * fix(version): remove some excessive log msgs from debug to silly level * test(fixtures): refactor builder functions for version file updates * test(fixtures): adjust build command to handle versions w/ build metadata * test(fixtures): fix gitflow repo that included an invalid build metadata string * test(fixtures): fix major_on_zero setting in repos to match expected behavior * test(cmd-version): add test cases to run an example repo rebuild w/ psr * test(cmd-version): enable git flow repo rebuild w/ psr test cases * fix(cmd-version): handle multiple prerelease token variants properly In the case where there are alpha and beta releases, we must only consider the previous beta release even if alpha releases exist due to merging into beta release only branches which have no changes considerable changes from alphas but must be marked otherwise. Resolves: #789 * fix(cmd-version): fix version determination algorithm to capture commits across merged branches * perf(cmd-version): refactor version determination algorithm for accuracy & speed * test(algorithm): refactor test to match new function signature * style(algorithm): drop unused functions & imports * test(algorithm): adapt test case for new DFS commit traversal implementation
…ensive test execution mode
Adds an automatic cancelation of in-progress pipelines to limit action minutes used (especially for e2e testing) when developer has already pushed a new update
* test(fixtures): improve changelog generator to filter by max version * test(fixtures): add repo fixture of a trunk only repo w/ dual version support * test(fixtures): add repo fixture of a trunk only repo w/ dual version support & prereleases * test(cmd-version): add rebuild repo tests for new dual version support repos * test(version-determination): adjust unit tests of increment_version logic This clarifies repeated function calls and pytest parameter names included the unclear assert diff. Adds additional tests to check bad states for failures and refactored to match new function signature. * fix(version-bump): increment based on current commit's history only Refactor duplicate logging messages and flow to process out odd cases in a fail fast methodology. This removes the reliance on any last full release that is not within the history of the current branch. Resolves: #861
…on versions (#1121) * ci(deps): bump `tj-actions/changed-files` from 45.0.4 to 45.0.5 Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * ci(deps): bump `python-semantic-release/publish-action` from 9.15.0 to 9.15.1 Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…es (#1190) Resolves: #846 * build(deps): add `deprecated~=1.2` for deprecation notices & sphinx documentation * refactor(noop): simplify text output during `--noop` execution * chore(mypy): set mypy configuration to ignore `dotty_dict` missing types * test(declarations): update unit tests for full file modification w/ tag formatted versions * test(cmd-version): add version stamp test to validate tag formatted version stamping * docs(configuration): add usage information for tag format version stamping
…`@` symbol separator (#1185) Resolves: #1156 * test(declaration): add unit tests of user-defined version stamping patterns * test(cmd-version): add test to demonstrate github actions yaml version tag stamping * docs(configuration): clarify `version_variables` config description & `@` separator usage --------- Co-authored-by: codejedi365 <codejedi365@gmail.com>
…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
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] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )