|
1 | 1 | # Changelog
|
2 | 2 |
|
| 3 | +## 0.33.0 (2025-03-02) |
| 4 | +[Compare the full difference.](https://github.com/callowayproject/bump-my-version/compare/0.32.2...0.33.0) |
| 5 | + |
| 6 | +### Fixes |
| 7 | + |
| 8 | +- Fixed warnings in documentation. [782077d](https://github.com/callowayproject/bump-my-version/commit/782077dc438007d4b585991788efe7c5a5c8c19f) |
| 9 | + |
| 10 | +- Refactored PEP621 tests into a class. [2a4f12a](https://github.com/callowayproject/bump-my-version/commit/2a4f12a68067bacf81ec536b884e9ec3afb16751) |
| 11 | + |
| 12 | + The tests are pretty much the same but renamed for clarity. |
| 13 | +- Fixed: allow omitting the current version in sample-config. [6b369fe](https://github.com/callowayproject/bump-my-version/commit/6b369fec76e9a45b919e32a85d0b894752f6374d) |
| 14 | + |
| 15 | + If the current version is explicitly left empty during the |
| 16 | + `sample-config` questionnaire, the resulting `tool.bumpversion` table |
| 17 | + now lacks a `current_version` key, and will fall back to PEP 621 |
| 18 | + `project.version` (if not dynamic). The instruction text specifically |
| 19 | + hints at this new functionality. |
| 20 | +### New |
| 21 | + |
| 22 | +- Add test for moveable tags. [df787f1](https://github.com/callowayproject/bump-my-version/commit/df787f153f1dcde8268e83ef3f035d018735e7bb) |
| 23 | + |
| 24 | +- New feature: retrieve and update the PEP 621 project version, if possible. [3032450](https://github.com/callowayproject/bump-my-version/commit/3032450098f14abeb0661c62442d1ca03b222e09) |
| 25 | + |
| 26 | + When determining the current version, and if |
| 27 | + `tool.bumpversion.current_version` is not set, attempt to retrieve the |
| 28 | + version from `project.version` à la PEP 621. If that setting is not |
| 29 | + set, or if the version is explicitly marked as dynamically set, then |
| 30 | + continue with querying SCM tags. |
| 31 | + |
| 32 | + When updating the configuration during bumping, if we previously |
| 33 | + successfully retrieved a PEP 621 version, then update the |
| 34 | + `project.version` field in `pyproject.toml` as well. We always update, |
| 35 | + even if the true current version was read from |
| 36 | + `tool.bumpversion.current_version` instead of `project.version`. |
| 37 | + |
| 38 | + The docs have been updated; specifically, the "multiple replacements in |
| 39 | + one file" howto and the reference for `current_version`. |
| 40 | + |
| 41 | + The tests have been adapted: the new `pep621_info` property would |
| 42 | + otherwise trip up the old test output, and the `None` default would trip |
| 43 | + up the TOML serializer. Additionally, new tests assert that |
| 44 | + `project.version` (and correspondingly, the `pep621_info` property) is |
| 45 | + correctly honored or ignored, depending on the other circumstances. |
| 46 | +### Other |
| 47 | + |
| 48 | +- [pre-commit.ci] pre-commit autoupdate. [59e8634](https://github.com/callowayproject/bump-my-version/commit/59e863415d9a9f7ef082978ccee7b27c36112ea1) |
| 49 | + |
| 50 | + **updates:** - [github.com/astral-sh/ruff-pre-commit: v0.9.6 → v0.9.7](https://github.com/astral-sh/ruff-pre-commit/compare/v0.9.6...v0.9.7) |
| 51 | + |
| 52 | +### Updates |
| 53 | + |
| 54 | +- Updated documentation. [8162dd8](https://github.com/callowayproject/bump-my-version/commit/8162dd852b874e36626ad01ad72ea892499a9817) |
| 55 | + |
| 56 | + |
3 | 57 | ## 0.32.2 (2025-02-22)
|
4 | 58 | [Compare the full difference.](https://github.com/callowayproject/bump-my-version/compare/0.32.1...0.32.2)
|
5 | 59 |
|
|
0 commit comments