Frappe ERPNext: App Version Management

How to change version info on your Frappe Custom app, and how to maintain tags and notes.

 · 1 min read

GitHub now can auto-block token and API key leaks for all repos





 On file __init__.py

__version__ = '2.0.1' 


Use Semantic Versioning


Follow the semantic versioning convention:

MAJOR: Breaking changes.

MINOR: Backward-compatible features.

PATCH: Bug fixes.


Example:

• v1.0.0: Initial release.

• v1.1.0: Added features.

• v1.1.1: Bug fixes.

• v2.0.0: Next major release.

• v2.1.0: Added features.

• v21.1: Bug fixes.


and on hooks.py file add following two lines  ( One time only )


from frappe import _

from . import __version__ as app_version


Create file for your version changes like version-2.1.1.md with following content ( Markdown format )

example below ( ### for heading )


Version 2.1.1

### Features
- Added encyrption features.
- Enhanced security for user authentication.

### Fixes
- Resolved memory leak issue in the data processing module.
- Fixed UI alignment on mobile devices.

### Contributors
- Farook K (@fkalpana) - Added encyrption features
- Husna M  (@HusnaMa) - Enhanced user authentication security.
- Malavika Gangadharan (@malavikag09) - Bug fixes in data processing module.

### Notes
- This version focuses on enhancing user experience and resolving critical issues reported in v2.0.0.



Push to GitHub

git tag -a v2.0.1 -F version-2.1.1.md

git push --tags


You can then do releases based on this tag , inside GitHub portal


Check these are properly reflected on Github. ( it will be like this https://github.com/frappe/erpnext/tags and https://github.com/frappe/erpnext/releases/tag/v15.47.4 )


Thahsin

Functional Consultant at ERPGulf

No comments yet

No comments yet. Start a new discussion.

Add Comment