Bump version to 1.7.0

- Add shared router architecture for event loops
- Add isolated event loops with ErlangEventLoop(isolated=True)

Author: benoitc

CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## 1.7.0 (2026-02-23)
+
+### Added
+
+- **Shared Router Architecture for Event Loops**
+  - Single `py_event_router` process handles all event loops (both shared and isolated)
+  - Timer and FD messages include loop identity for correct dispatch
+  - Eliminates need for per-loop router processes
+  - Handle-based Python C API using PyCapsule for loop references
+
+- **Isolated Event Loops** - Create isolated event loops with `ErlangEventLoop(isolated=True)`
+  - Default (`isolated=False`): uses the shared global loop managed by Erlang
+  - Isolated (`isolated=True`): creates a dedicated loop with its own pending queue
+  - Full asyncio support (timers, FD operations) for both modes
+  - Useful for multi-threaded Python applications where each thread needs its own loop
+  - See `docs/asyncio.md` for usage and architecture details
+
 ## 1.6.1 (2026-02-22)
 
 ### Fixed
@@ -18,12 +35,6 @@
 
 ### Added
 
-- **Isolated Event Loops** - Create isolated event loops with `ErlangEventLoop(isolated=True)`
-  - Each isolated loop has its own pending queue
-  - Full asyncio support (timers, FD operations) via shared router
-  - Useful for multi-threaded Python applications
-  - See `docs/asyncio.md` for usage and architecture details
-
 - **Python Logging Integration** - Forward Python's `logging` module to Erlang's `logger`
   - `py:configure_logging/0,1` - Setup Python logging to forward to Erlang
   - `erlang.ErlangHandler` - Python logging handler that sends to Erlang

src/erlang_python.app.src

@@ -1,6 +1,6 @@
 {application, erlang_python, [
     {description, "Execute Python applications from Erlang using dirty NIFs"},
-    {vsn, "1.6.1"},
+    {vsn, "1.7.0"},
     {registered, [py_pool]},
     {mod, {erlang_python_app, []}},
     {applications, [