Comments (12)
.. that is, if you don't use --dry-run
, there is 0.9.3
in the .bumpversion.cfg
afterwards and 0.7.2
in in myp/__init__.py
?
Could you try using the new files config syntax introduced in 0.5.0
, for your case that would be removing
files = myp/__init__.py
and adding as a separate section
[bumpversion:file:myp/__init__.py]
and see whether the result is different (see README for details) ?
from bumpversion.
Sounds like a bug in bumpversion to me, even if only when importing pre-0.5 config files.
from bumpversion.
do you still want me to try what you suggested ?
from bumpversion.
Using the new syntax could be a workaround that might work for you until I have a regression test at hand / released a fix if I can verify the defect.
from bumpversion.
Not better with the new syntax. the part is applied to the file while the new-version value is only applied to .bumpversion.cfg
from bumpversion.
@peritus Can you label this issue as bug ?
from bumpversion.
Yes it's a bug ;)
from bumpversion.
Thanks
from bumpversion.
Has this been fixed yet? I'm running into this problem with v0.5.1.
[bumpversion]
current_version = 0.8.0
[bumpversion:file:project/__init__.py]
# project/__init__.py
__version__ = "0.8.0"
$ bumpversion patch --allow-dirty --verbose --new-version 0.9.0
# Reading config file .bumpversion.cfg:
# [bumpversion]
# current_version = 0.8.0
#
# [bumpversion:file:project/__init__.py]
#
#
# Parsing version '0.8.0' using regexp '(?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)'
# Parsed the following values: major=0, minor=8, patch=0
# Attempting to increment part 'patch'
# Values are now: major=0, minor=8, patch=1
# New version will be '0.9.0'
# Asserting files project/__init__.py contain the version string:
# Found '0.8.0' in project/__init__.py at line 0: __version__ = "0.8.0"
# Changing file project/__init__.py:
# --- a/project/__init__.py
# +++ b/project/__init__.py
# @@ -1,3 +1,3 @@
# -__version__ = "0.8.0"
# +__version__ = "0.8.1"
# Writing to config file .bumpversion.cfg:
# [bumpversion]
# current_version = 0.9.0
#
# [bumpversion:file:project/__init__.py]
#
#
# Would prepare Git commit
# Would prepare Git commit
# Would add changes in file 'project/__init__.py' to Git
# Would add changes in file '.bumpversion.cfg' to Git
# Would commit to Git with message 'Bump version: 0.8.0 → 0.9.0'
# Would tag 'v0.9.0' in Git
from bumpversion.
@petebrowne the PR is still opened, so I guess it's still pending
from bumpversion.
This has not been fixed yet, willing to merge patches including tests and docs (ok, well, one regression test exists already).
Sent from my pocket calculator
On 21 Mar 2015, at 20:48, cscetbon [email protected] wrote:
@petebrowne the PR is still opened, so I guess it's still pending
�
Reply to this email directly or view it on GitHub.
from bumpversion.
Awesome! When will this be released to pypi?
from bumpversion.
Related Issues (20)
- Multi-line `replace` doesn't work for lines starting with `#` HOT 2
- Missing allowed 'part' values in commandline help HOT 2
- All strings matching current version are bumping up in setup.py file. HOT 2
- Issue while using search and replace configurations. HOT 2
- Do not fail on the dirty state during the dry-run HOT 1
- How to keep the metadata part when bumping version?
- bump version number in filename
- Bumpversion --list returned non-zero exit status 1 HOT 1
- Improvement README.rst
- TypeError: 'NoneType' object is not iterable HOT 1
- Release version from working branch
- search-replace falls back to plain version lookup in some cases HOT 1
- help need: error while serialize following pattern (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)\.(?P<build>\d+)
- No Pre-Release Tags if Major Version is 0 HOT 1
- bumpversion w/ added "commit" part adding additional parts to files
- Add ability to specify a value of a part of version only HOT 1
- Need better documentation on multiline support for `search` and `replace`
- Is it possible to allow {current_[part]} / {new_[part]} in search/replace?
- Dependencies versions in pyproject.toml altered casually
- Is it possible to make numbered beta versions like in npm?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bumpversion.