Migration script: handle versioning with `hatch`

[Jeremy Tuloup]

Problem

The migration script currently defines some tbump configuration by default:

hatch-jupyter-builder/hatch_jupyter_builder/migrate/_migrate.py

Lines 172 to 191 in ba9f6fe

 # Handle versioning with tbump - allows for static versioning and makes 
 # it easier to use jupyter_releaser. 
 data["project"]["version"] = current_version 
 data["project"].pop("dynamic", None) 
  
 tbump_table = tool_table.setdefault("tbump", {}) 
 tbump_table["version"] = dict( 
     current=current_version, 
     regex=r""" 
       (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)((?P<channel>a|b|rc|.dev)(?P<release>\d+))? 
     """.strip(), 
 ) 
 tbump_table["git"] = dict(message_template=r"Bump to {new_version}", tag_template=r"v{new_version}") 
 tbump_table["field"] = [dict(name="channel", default=""), dict(name="release", default="")] 
 tbump_table["file"] = [ 
     dict( 
         src="pyproject.toml", 
         version_template='version = "{major}.{minor}.{patch}{channel}{release}"', 
     ) 
 ] 

Proposed Solution

Since hatch supports versioning, it could be interesting to use hatch by default instead.

Additional context

Spotted when using the migration script recently.

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉