magicbox-dk 0.0.2__tar.gz → 0.0.2.dev1__tar.gz

magicbox_dk-0.0.2.dev1/.bumpversion.toml

@@ -0,0 +1,53 @@
+# bump-my-version configuration
+# Follows PEP 440 versioning standards for Python packages
+# https://peps.python.org/pep-0440/
+
+[tool.bumpversion]
+current_version = "0.0.2.dev1"
+
+allow_dirty = false # Require clean working directory
+commit = false # Don't auto-commit (let user control git)
+tag = true
+sign_tags = false # Don't sign tags
+
+# major.minor.patch with an optional `.devN` pre-release.
+parse = """(?x)
+    (?P<major>0|[1-9]\\d*)\\.
+    (?P<minor>0|[1-9]\\d*)\\.
+    (?P<patch>0|[1-9]\\d*)
+    (?:\\.dev(?P<dev>0|[1-9]\\d*))?   # optional .dev pre-release
+    """
+
+serialize = [
+    "{major}.{minor}.{patch}.dev{dev}",
+    "{major}.{minor}.{patch}",
+]
+
+# `.dev` part : omitted when 0 (final release).
+[tool.bumpversion.parts.dev]
+first_value = "1"
+optional_value = "0"
+
+# Files to update when bumping version
+
+# pyproject.toml : version field in the [project] section.
+# (Config lives here, NOT in pyproject.toml, so bump-my-version does NOT
+#  natively touch [project].version — this explicit block is required and
+#  matches a single, unambiguous line.)
+[[tool.bumpversion.files]]
+filename = "pyproject.toml"
+search = 'version = "{current_version}"'
+replace = 'version = "{new_version}"'
+
+# uv.lock : keep the magicbox-dk package entry in sync.
+[[tool.bumpversion.files]]
+filename = "uv.lock"
+regex = true
+search = 'name = "magicbox-dk"\nversion = "{current_version}"'
+replace = 'name = "magicbox-dk"\nversion = "{new_version}"'
+
+# Usage:
+#   bump-my-version bump dev     # 0.0.1 -> 0.0.1.dev1 -> 0.0.1.dev2 ...
+#   bump-my-version bump patch   # 0.0.1.dev2 -> 0.0.2   (drops .dev)
+#   bump-my-version bump minor   # 0.0.1 -> 0.1.0
+#   bump-my-version bump major   # 0.0.1 -> 1.0.0

{magicbox_dk-0.0.2 → magicbox_dk-0.0.2.dev1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: magicbox-dk
-Version: 0.0.2
+Version: 0.0.2.dev1
 Summary: Magicbox for help DigitalKin developpers.
 Author-email: Alexandre TRESALLET <a.tresall@digitalkin.ai>
 License-Expression: MIT

magicbox_dk-0.0.2.dev1/pyproject.toml

@@ -0,0 +1,74 @@
+[project]
+
+    description     = "Magicbox for help DigitalKin developpers."
+    license         = "MIT"
+name = "magicbox-dk"
+    readme          = "README.md"
+    requires-python = ">=3.10"
+
+version = "0.0.2.dev1"
+
+    keywords        = [ "digitalkin", "magicbox", "kin", "sdk" ]
+
+
+    dependencies = [
+        "typer>=0.25.1",
+        "pydantic>=2.13.4",
+        "pyyaml>=6.0.3",
+        "questionary>=2.0.0",
+        "rich>=13.0.0",
+        "jinja2>=3.1",
+    ]
+
+[[project.authors]]
+email = "a.tresall@digitalkin.ai"
+name = "Alexandre TRESALLET"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["cli"]
+# Écarte les artefacts lourds/locaux des dossiers embarqués (surtout
+# `services/chainlit/.venv`, ~240 Mo) — seul le source nécessaire au build
+# Docker doit partir dans le wheel.
+exclude = [
+    "**/.venv",
+    "**/node_modules",
+    "**/__pycache__",
+    "**/*.pyc",
+    "**/.ruff_cache",
+    "**/.mypy_cache",
+    "**/.pytest_cache",
+    "**/.DS_Store",
+    "**/dist",
+    "**/build",
+]
+
+# Les templates versionnés `configs/`, `docker/` et les sources buildées
+# `services/` (image chainlit, bundle horizon) vivent à la racine du dépôt
+# (pratique en dev et pour les builds Docker) mais sont embarqués **sous** le
+# package dans le wheel (`cli/configs`, `cli/docker`, `cli/services`). Nichés
+# sous `cli/` plutôt qu'en top-level de `site-packages` pour éviter d'écraser
+# d'autres paquets (notamment le SDK PyPI `docker`). Le compose chainlit résout
+# `services/chainlit` contre `--project-directory` = `REPO_ROOT`, calculé dans
+# `cli/settings.py:_DATA_ROOT`.
+[tool.hatch.build.targets.wheel.force-include]
+"configs" = "cli/configs"
+"docker" = "cli/docker"
+"services" = "cli/services"
+
+[dependency-groups]
+dev = [
+    "pytest>=9.1.0",
+    "bump-my-version>=1.2.0",
+]
+
+[project.scripts]
+    digitalkin = "cli.main:app"
+    dk = "cli.main:app"
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-ra"

{magicbox_dk-0.0.2 → magicbox_dk-0.0.2.dev1}/uv.lock

@@ -166,7 +166,7 @@ wheels = [
 
 [[package]]
 name = "magicbox-dk"
-version = "0.0.1"
+version = "0.0.2.dev1"
 source = { editable = "." }
 dependencies = [
     { name = "jinja2" },

magicbox_dk-0.0.2/pyproject.toml

@@ -1,87 +0,0 @@
-[project]
-
-    description     = "Magicbox for help DigitalKin developpers."
-    license         = "MIT"
-name = "magicbox-dk"
-    readme          = "README.md"
-    requires-python = ">=3.10"
-
-    version         = "0.0.2"
-
-    keywords        = [ "digitalkin", "magicbox", "kin", "sdk" ]
-
-
-    dependencies = [
-        "typer>=0.25.1",
-        "pydantic>=2.13.4",
-        "pyyaml>=6.0.3",
-        "questionary>=2.0.0",
-        "rich>=13.0.0",
-        "jinja2>=3.1",
-    ]
-
-[[project.authors]]
-email = "a.tresall@digitalkin.ai"
-name = "Alexandre TRESALLET"
-
-[build-system]
-requires = ["hatchling"]
-build-backend = "hatchling.build"
-
-[tool.hatch.build.targets.wheel]
-packages = ["cli"]
-
-# Les templates versionnés `configs/` et `docker/` vivent à la racine du dépôt
-# (pratique en dev et pour les builds Docker) mais sont embarqués **sous** le
-# package dans le wheel (`cli/configs`, `cli/docker`). Nichés sous `cli/` plutôt
-# qu'en top-level de `site-packages` pour éviter d'écraser d'autres paquets
-# (notamment le SDK PyPI `docker`). La résolution runtime est dans
-# `cli/settings.py:_DATA_ROOT`.
-[tool.hatch.build.targets.wheel.force-include]
-"configs" = "cli/configs"
-"docker" = "cli/docker"
-
-[dependency-groups]
-dev = [
-    "pytest>=9.1.0",
-    "bump-my-version>=1.2.0",
-]
-
-[project.scripts]
-    digitalkin = "cli.main:app"
-    dk = "cli.main:app"
-
-[tool.pytest.ini_options]
-testpaths = ["tests"]
-addopts = "-ra"
-
-[tool.bumpversion]
-current_version = "0.0.2"
-allow_dirty = false
-commit = true
-message = "chore(release): bump version {current_version} → {new_version}"
-tag = true
-tag_name = "v{new_version}"
-tag_message = "Release v{new_version}"
-sign_tags = false
-
-# PEP 440 : major.minor.patch avec un pré-release `.devN` optionnel.
-parse = """(?x)
-    (?P<major>0|[1-9]\\d*)\\.
-    (?P<minor>0|[1-9]\\d*)\\.
-    (?P<patch>0|[1-9]\\d*)
-    (?:\\.dev(?P<dev>0|[1-9]\\d*))?
-"""
-serialize = [
-    "{major}.{minor}.{patch}.dev{dev}",
-    "{major}.{minor}.{patch}",
-]
-
-[tool.bumpversion.parts.dev]
-first_value = "0"
-optional_value = "0"
-
-[[tool.bumpversion.files]]
-filename = "pyproject.toml"
-search = 'version         = "{current_version}"'
-replace = 'version         = "{new_version}"'