-
The `bumpversion` workflow runs `poetry` `bumpversion` upon mege to main.
That seems too often, usually on bumps once per release only, and there are typically more locations to update (docs, read…
-
Let's use a shared and approved "version bumper" script/software and cofigure a template workflow to be used on PR open towards master/main which bumps version automatically.
-
`bumpversion` tends to mess up the config. It would be better to split it to `.bumpversionrc`, so it doesn't messes up the `setup.cfg`.
ziima updated
4 years ago
-
bumpversion uses trailing spaces and tabs if it updates it's own configuration. As long as the configuration is kept in a separate `.bumpversion` file this is just a cosmetic issue.
But since release…
-
### Environment
* PIP Chill version: dev
* Python version: 3.12 but does not matter
* Operating System: MacOS
### Description
This is a followup from PR #75.
Test fails if a packag…
-
### How are you running Renovate?
Self-hosted
### If you're self-hosting Renovate, tell us what version of Renovate you run.
32.6.1
### Please select which platform you are using if self-h…
-
[pbr](https://docs.openstack.org/) has a much larger functionality than [Bumpversion](https://github.com/peritus/bumpversion). So it can not only update versions. It updates version numbers based on g…
-
In a "typical" project directory structure:
```python
project/
|
└───.venv/
|
└───project/
| |
| └─── file1.py
| |
| └─── file2.py
|
└─── .bumpversion.cfg
```
`bumpversion` w…
-
Many bumpversion and postrelease tests fails at OpenIndiana. Typical example is this:
```
File "$(BUILD_DIR)/zest/releaser/tests/bumpversion.txt", line 44, in bumpversion.txt
Failed example:
…
-
look into adding configurations, regex, shorthand to bumpversion cfg for use in our file searches
as-is just replaces current_version & new_version per bump2version, but regex etc. would be nice