Conversation
Get it from recipe file instead of git-tag.
Reset version back down to v2.x from v4.0.0.2 See link below for Semanctic Versioning & .NET https://codingforsmarties.wordpress.com/2016/01/21/how-to-version-assemblies-destined-for-nuget/
Configuration based from gh:bumpversion:issues:77#issuecomment-130696156 Usage: bumpversion major -> increases major and adds `dev` if not present bumpversion minor -> increases minor and adds `dev` if not present bumpversion release -> drop the `dev` portion
bf1e18e to
5a7d297
Compare
|
@vmuriart so why not versioneer which is also internally used by conda-build? bumpversion has stalled for 2 years and it is also used 10 times less on github: https://github.com/search?l=Python&q=bumpversion&ref=searchresults&type=Code&utf8=%E2%9C%93 Is it easier to use or has some features? |
|
I forgot to add my reasoning, thanks for the reminder.
the
|
|
can you add instructions to developer docs? https://github.com/pythonnet/pythonnet/wiki/Development-setup |
|
Added the documentation to the |

What does this implement/fix? Explain your changes.
Automate version update.
Fixes conda-recipe version from lagging (used to look at last git-tag)
Fixes and centralizes AssemblyInfo version information
Does this close any currently open issues?
Closes #319
Any other comments?
Based from: peritus/bumpversion#77 (comment)
Example usage:
bumpversion patch:0.1.0->0.1.1.dev0bumpversion release:0.1.1.dev0->0.1.1bumpversion minor:0.1.1->0.2.0.dev0bumpversion dev:0.2.0.dev0->0.2.0.dev1bumpversion release:0.2.0.dev1->0.2.0I chose to not add auto-commit/auto-tag. For one, its broken on PY3 and also would prefer testing out before potentially causing the git-history to get extremely messy.
Checklist
Check all those that are applicable and complete.
AUTHORS