Skip to content

Conversation

@davidhyman
Copy link
Contributor

Bumps the semver dependency; let's see if the tests are happy now.

It now supports some of the features we were doing in autoversion, so might replace the SemVerSigFig code - but that's for a later PR.

davidhyman and others added 30 commits February 26, 2019 12:52
to support incrementing prerelease and build flags
add a couple of extra tests
have to clear the config as it's operating as a global with mutable dicts - fine in CLI but breaks in tests
gives better handling of situation where user is starting from `0.0.0` with no tags.
whereas glob returns files relative to cwd
example config for `trigger_patterns`:
```
                "newsfiles/*.bugfix": "patch",
                "newsfiles/*.doc": "patch",
                "newsfiles/*.feature": "minor",
                "newsfiles/*.major": "major",
                "newsfiles/*.minor": "minor",
                "newsfiles/*.patch": "patch",
                "newsfiles/*.removal": "major",
```
Previously, the `new_version` was printed, which included prerelease tags, even if the `--release` flag was passed. This seemed wrong, but does change the behaviour - if the prerelease version is needed on stdout, don't pass the `--release` flag.
previously, tag templates like `v{version}` would end up looking like

`^(.*)v$`

Because the `10*v` is position-invariant and `.replace` replaces the first match. Using a position-specific string (like, any string with a variety of characters ...) resolves this issue.
Bugfix/bad placeholder (SANE-484)
@acabarbaye acabarbaye closed this May 18, 2021
@acabarbaye acabarbaye reopened this May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants