Release 0.0.2 prep

Author: giangtruongvu

CHANGELOG.md

@@ -0,0 +1,38 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [0.0.2] - 2026-04-10
+
+### Fixed
+
+- Fixed pytest plugin auto-loading via the `pytest11` entry point.
+- Fixed the `pytest_unconfigure` hook signature in `revitdevtool_pytest.plugin` so Pluggy accepts the plugin during pytest startup.
+- Restored the expected standalone package behavior so `RevitDevTool.PyTest` can be discovered and activated by a normal Python/pytest environment before connecting to Revit.
+
+### Changed
+
+- Aligned the published package metadata name with the recommended normalized package name `revitdevtool_pytest`.
+
+### Notes
+
+- This release is intended as a bugfix release for the `0.0.1` package.
+- No user-facing CLI options are changed in this release.
+- This name alignment is intended to remain compatible with existing PyPI installs because Python package indexes and installers normalize `.`, `-`, and `_` in distribution names.
+
+## [0.0.1] - 2026-04-09
+
+### Added
+
+- Initial standalone `pytest` plugin package for running Revit API tests through the RevitDevTool Named Pipe bridge.
+- Automatic discovery of running Revit instances through named pipes.
+- Optional Revit auto-launch flow via `--revit-launch` and `--revit-version`.
+- Remote test execution by intercepting `pytest_pyfunc_call` and forwarding serialized test code to Revit.
+- Support for explicit pipe targeting with `--revit-pipe`.
+- Per-test timeout and launch timeout configuration.
+- Revit startup dialog resolver integration.
+- Example test suite and VS Code integration guidance in the project documentation.
+
+### Notes
+
+- `0.0.1` introduced the core test bridge workflow, but the published package contains a plugin loading issue fixed in `0.0.2`.

README.md

@@ -10,9 +10,29 @@ Tests run inside a live Revit process — write standard pytest, execute remotel
 ## Installation
 
 ```bash
+pip install revitdevtool_pytest
+```
+
+Recommended package name for manifests and package managers such as Pixi:
+
+```bash
+revitdevtool_pytest
+```
+
+`pip` normalizes package names, so the following forms are equivalent when installing from PyPI:
+
+```bash
+pip install revitdevtool_pytest
+pip install revitdevtool-pytest
 pip install RevitDevTool.PyTest
 ```
 
+The Python import/module name used by the package is:
+
+```python
+import revitdevtool_pytest
+```
+
 ## Dependencies
 
 | Package | Version |

pyproject.toml

@@ -3,8 +3,8 @@ requires = ["hatchling"]
 build-backend = "hatchling.build"
 
 [project]
-name = "RevitDevTool.PyTest"
-version = "0.0.1"
+name = "revitdevtool_pytest"
+version = "0.0.2"
 description = "pytest plugin for testing Revit API code via RevitDevTool Named Pipe bridge"
 readme = "README.md"
 license = "MIT"

src/revitdevtool_pytest/plugin.py

@@ -126,7 +126,7 @@ def pytest_pyfunc_call(pyfuncitem: pytest.Function) -> object:
     pytest.fail(msg, pytrace=False)
 
 
-def pytest_unconfigure(_config: pytest.Config) -> None:
+def pytest_unconfigure(config: pytest.Config) -> None:
     global _bridge, _dialog_resolver
     if _dialog_resolver is not None:
         _dialog_resolver.stop()