chore(repo,core,mkdocs): bump version to 0.3.0

owenthcarey · owenthcarey · commit 64d7c1cfb448 · 2025-10-22T14:19:09.000-07:00
diff --git a/docs/api/pythonnative.md b/docs/api/pythonnative.md
@@ -2,7 +2,7 @@
 
 API reference will be generated here via mkdocstrings.
 
-Key flags and helpers (0.2.0):
+Key flags and helpers:
 
 - `pythonnative.utils.IS_ANDROID`: platform flag with robust detection for Chaquopy/Android.
 - `pythonnative.utils.get_android_context()`: returns the current Android Activity/Context when running on Android.
diff --git a/docs/concepts/components.md b/docs/concepts/components.md
@@ -2,7 +2,7 @@
 
 High-level overview of PythonNative components and how they map to native UI.
 
-## Constructor pattern (0.2.0)
+## Constructor pattern
 
 - All core components share a consistent, contextless constructor on both platforms.
 - On Android, a `Context` is acquired implicitly from the current `Activity` set by `pn.Page`.
@@ -30,7 +30,7 @@ Notes:
 - `pn.Page` stores the Android `Activity` so components like `pn.Button()` and `pn.Label()` can construct their native counterparts.
 - If you construct views before the `Page` is created on Android, a runtime error will be raised because no `Context` is available.
 
-## Core components (0.2.0)
+## Core components
 
 Stabilized with contextless constructors on both platforms:
 
diff --git a/pyproject.toml b/pyproject.toml
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pythonnative"
-version = "0.2.0"
+version = "0.3.0"
 description = "Cross-platform native UI toolkit for Android and iOS"
 authors = [
   { name = "Owen Carey" }
diff --git a/src/pythonnative/__init__.py b/src/pythonnative/__init__.py
@@ -1,7 +1,7 @@
 from importlib import import_module
 from typing import Any, Dict
 
-__version__ = "0.2.0"
+__version__ = "0.3.0"
 
 __all__ = [
     "ActivityIndicatorView",
