chore: ignore .env and document 3.1.x fixes in the 3.2.0 notes

- gitignore .env / .env.* (keep .env.example) to avoid committing secrets.
- release notes: refine the import-migration table and add the #624/#625
  and #627 bug-fix entries for the upcoming 3.2.0 release.

Signed-off-by: Fernando Macedo <fgmacedo@gmail.com>

Author: fgmacedo

.gitignore

@@ -85,3 +85,8 @@ tmp/
 
 # Local specs
 specs/
+
+# Environment files (secrets)
+.env
+.env.*
+!.env.example

docs/releases/3.2.0.md

@@ -74,19 +74,20 @@ The experimental `statemachine.io.scxml` internals were promoted into a format-n
 IO core (see *What's new* below). Code that imported implementation modules directly must
 update its imports:
 
-| Before | After |
+| Before (3.1.x) | After (3.2.0) |
 |---|---|
 | `statemachine.io.scxml.schema` | `statemachine.io.model` |
-| `statemachine.io.scxml.datamodel` | `statemachine.io.evaluators` |
 | `statemachine.io.scxml.parser` | `statemachine.io.scxml.reader` |
 | generic helpers in `statemachine.io.scxml.actions` | `statemachine.io.actions` |
+| `protected_attrs` / `_eval` in `statemachine.io.scxml.actions` | `statemachine.io.evaluators` |
 | `EventDataWrapper` etc. in `statemachine.io.scxml.actions` | `statemachine.io.system_variables` |
 | `SCXMLInvoker` in `statemachine.io.scxml.invoke` | `Invoker` in `statemachine.io.invoke` |
-| `statemachine.io.processor.GenericProcessor` | `statemachine.io.interpreter.Interpreter` (+ `statemachine.io.builder`) |
 
-`statemachine.io.scxml.processor.SCXMLProcessor` (now a thin `Interpreter` wrapper, minus
-the removed `parse_scxml_file` — use `io.load` for files) and
-`statemachine.io.create_machine_class_from_definition` keep their behavior.
+`statemachine.io.scxml.processor.SCXMLProcessor` (now a thin wrapper over the new
+format-neutral runtime, minus the removed `parse_scxml_file`; use `io.load` for files) and
+`statemachine.io.create_machine_class_from_definition` keep their behavior. The runtime
+itself moved into the new, SCXML-agnostic `statemachine.io.interpreter.Interpreter` and
+`statemachine.io.builder` (see *Architecture* below).
 
 ## What's new in 3.2.0
 
@@ -145,4 +146,29 @@ python-statemachine[io]          # both of the above
 
 ## Bug fixes in 3.2.0
 
-TODO
+### Sibling compound states with same-named children no longer collide
+
+A `StateChart` with sibling compound states whose children reuse the same local
+`id` (e.g. each region declares an `a` and a `b`) but carry distinct `value=`
+identifiers would collapse in the internal instance-state map, which was keyed by
+`state.id`. The duplicate ids overwrote each other, so dispatching an event
+resolved to the wrong `State` instance and raised `TransitionNotAllowed`.
+
+Instance states are now keyed by `state.value` (globally unique, the canonical
+identifier already used by `states_map`), fixing dispatch for nested and parallel
+configurations that repeat child names.
+
+[#624](https://github.com/fgmacedo/python-statemachine/issues/624),
+[#625](https://github.com/fgmacedo/python-statemachine/pull/625).
+
+### Async `invoke` no longer cancels itself on its own `done.invoke`
+
+When an async `invoke` completed and its `done.invoke` event triggered a
+transition out of the owning state, the cancel-on-exit path could cancel the
+invocation's own task while it was still running. The `CancelledError` surfaced at
+the next `await`, so the target state's `on_enter` callback never finished.
+
+The engine now skips self-cancellation when the invocation's task is the currently
+running task, letting the originating handler complete normally.
+
+[#627](https://github.com/fgmacedo/python-statemachine/pull/627).