pytest-allure-host 0.1.1__tar.gz

pytest_allure_host-0.1.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Allure Hosting Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

pytest_allure_host-0.1.1/PKG-INFO

@@ -0,0 +1,305 @@
+Metadata-Version: 2.4
+Name: pytest-allure-host
+Version: 0.1.1
+Summary: Publish Allure static reports to private S3 behind CloudFront with history preservation
+License-Expression: MIT
+License-File: LICENSE
+Keywords: allure,pytest,aws,s3,cloudfront,reporting
+Author: Allure Hosting Maintainers
+Requires-Python: >=3.9,<4.0
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: Software Development :: Testing
+Classifier: Framework :: Pytest
+Classifier: Development Status :: 3 - Alpha
+Classifier: Operating System :: OS Independent
+Requires-Dist: PyYAML (>=6,<7)
+Requires-Dist: boto3 (>=1.28,<2.0)
+Project-URL: Bug Tracker, https://github.com/darrenrabbs/allurehosting/issues
+Project-URL: Changelog, https://github.com/darrenrabbs/allurehosting/releases
+Project-URL: Documentation, https://github.com/darrenrabbs/allurehosting#readme
+Project-URL: Homepage, https://github.com/darrenrabbs/allurehosting
+Project-URL: Repository, https://github.com/darrenrabbs/allurehosting
+Description-Content-Type: text/markdown
+
+# pytest-allure-host
+
+![CI](https://github.com/darrenrabbs/allurehosting/actions/workflows/ci.yml/badge.svg)
+![CodeQL](https://github.com/darrenrabbs/allurehosting/actions/workflows/codeql.yml/badge.svg)
+![PyPI - Version](https://img.shields.io/pypi/v/pytest-allure-host.svg)
+![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)
+
+Publish Allure static reports to private S3 behind CloudFront with history preservation and SPA-friendly routing.
+
+See `docs/architecture.md` and `.github/copilot-instructions.md` for architecture and design constraints.
+
+## Features
+
+- Generate Allure static report from `allure-results`
+- Preserve history by pulling `latest/history` before generation
+- Upload to S3 under `<project>/<branch>/<run_id>/` and update `<project>/<branch>/latest/`
+- Two-phase latest update: upload to `latest_tmp/`, swap into `latest/`, write `LATEST_READY` marker
+- Optional retention: keep only N newest runs (`--max-keep-runs`)
+- Correct caching headers: `index.html` and `widgets/` → `no-cache`; assets → immutable
+- Optional TTL tagging on objects (`--ttl-days`) for S3 lifecycle policies
+- Optional summary JSON output for CI
+- Best-effort manifest at `runs/index.json` with new run metadata
+- Lightweight pointer file `latest.json` (branch root)
+- Human-friendly HTML index at `runs/index.html` for navigating past runs
+  - Columns: Run ID, raw epoch, UTC Time (human readable), Size (pretty units), P/F/B (passed/failed/broken counts), links to the immutable run and the moving latest
+  - Newest run highlighted with a star (★) and soft background
+
+## Requirements
+
+- Python 3.9+
+- AWS credentials with S3 access to the target bucket
+- Allure commandline available on PATH (e.g., via Allure CLI or allure-pytest)
+
+## S3 layout and caching
+
+- Keys:
+  - `s3://<bucket>/<prefix>/<project>/<branch>/<run_id>/...`
+  - `s3://<bucket>/<prefix>/<project>/<branch>/latest/...`
+  - `s3://<bucket>/<prefix>/<project>/<branch>/runs/index.json` (manifest)
+  - `s3://<bucket>/<prefix>/<project>/<branch>/runs/index.html` (HTML index)
+  - `s3://<bucket>/<prefix>/<project>/<branch>/latest.json` (pointer)
+- Two-phase swap writes a `LATEST_READY` marker file under `latest/` when ready.
+- Cache-Control:
+  - `index.html`: `no-cache`
+  - files under `widgets/`: `no-cache`
+  - everything else: `public, max-age=31536000, immutable`
+
+## CLI usage
+
+Install locally for development:
+
+```bash
+pip install -e .[dev]
+```
+
+Run the publisher after tests generate `allure-results`:
+
+```bash
+publish-allure \
+  --bucket your-bucket \
+  --prefix reports \
+  --project demo \
+  --branch main \
+  --cloudfront https://reports.example.com \
+  --ttl-days 30 \
+  --max-keep-runs 10
+```
+
+Flags (CLI):
+
+- `--bucket` (required): S3 bucket name
+- `--prefix` (default: `reports`): Root prefix
+- `--project` (required): Project name
+- `--branch` (default: `$GIT_BRANCH` or `main`)
+- `--run-id` (default: `$ALLURE_RUN_ID` or `YYYYMMDD-HHMMSS`)
+- `--cloudfront` (optional; default: `$ALLURE_CLOUDFRONT`)
+- `--results` (default: `allure-results`): Input directory
+- `--report` (default: `allure-report`): Output directory
+- `--ttl-days` (optional): Add `ttl-days=<N>` object tag
+- `--max-keep-runs` (optional): Keep N newest run prefixes, delete older
+- `--summary-json <path>`: Write machine-readable summary
+- `--check`: Preflight validation (AWS access, allure, inputs)
+- `--dry-run`: Print planned prefixes and sample headers, no upload
+- `--s3-endpoint`: Custom S3 endpoint (e.g. `http://localhost:4566` for LocalStack)
+
+Environment fallbacks:
+
+- `GIT_BRANCH` → `--branch` default
+- `ALLURE_RUN_ID` → `--run-id` default
+- `ALLURE_CLOUDFRONT` → `--cloudfront` default
+- `ALLURE_S3_ENDPOINT` → `--s3-endpoint` default (LocalStack / custom S3)
+
+## Pytest plugin usage
+
+Run tests and publish during terminal summary:
+
+```bash
+pytest \
+  --allure-bucket your-bucket \
+  --allure-prefix reports \
+  --allure-project demo \
+  --allure-branch main \
+  --allure-cloudfront https://reports.example.com \
+  --allure-ttl-days 30 \
+  --allure-max-keep-runs 10
+```
+
+Flags (pytest):
+
+- `--allure-bucket` (required)
+- `--allure-prefix` (default: `reports`)
+- `--allure-project` (required)
+- `--allure-branch` (default: `$GIT_BRANCH` or `main`)
+- `--allure-run-id` (default: `$ALLURE_RUN_ID` or `YYYYMMDD-HHMMSS`)
+- `--allure-cloudfront` (optional; default: `$ALLURE_CLOUDFRONT`)
+- `--allure-ttl-days` (optional)
+- `--allure-max-keep-runs` (optional)
+- `--allure-summary-json <path>` (optional)
+- `--allure-check` / `--allure-dry-run` (optional)
+
+## Preflight and dry-run
+
+- `--check`/`--allure-check` verifies:
+  - S3 bucket reachability (HeadBucket/List)
+  - `allure-results` exists and is non-empty
+  - Allure CLI exists on PATH
+- `--dry-run`/`--allure-dry-run` prints planned prefixes and sample headers; no uploads occur.
+
+## Outputs
+
+- S3 prefixes: run and latest
+- Optional CDN URLs (if `--cloudfront` provided)
+- `runs/index.json` manifest updated with new run entry
+- `runs/index.html` HTML table of recent runs (newest first) with columns: Run ID, Epoch, UTC Time, Size, P/F/B, Run, Latest (newest row highlighted with ★)
+- `latest.json` pointer to current run (simple machine-readable metadata)
+- Optional `--summary-json` with sizes, file counts, and destination URLs
+- `latest/LATEST_READY` marker indicates the swap is complete
+
+## Security
+
+See `SECURITY.md` for how to report vulnerabilities. Never open a public issue containing sensitive details.
+
+## Badges / Status
+
+- CI: multi-version test matrix + lint/security
+- CodeQL: static code analysis
+
+## Contributing
+
+See `CONTRIBUTING.md` and follow the pre-commit hooks (`pre-commit install`).
+
+## Release
+
+Tagged versions (`vX.Y.Z`) are published to PyPI automatically via GitHub OIDC.
+
+## CI examples
+
+GitHub Actions (CLI):
+
+```yaml
+jobs:
+  tests:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.11" }
+      - run: pip install .[dev]
+      - run: pytest -q
+      - name: Publish Allure
+        env:
+          AWS_REGION: us-east-1
+          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+          GIT_BRANCH: ${{ github.ref_name }}
+        run: >-
+          publish-allure --bucket $BUCKET --prefix reports --project demo
+          --branch "$GIT_BRANCH" --cloudfront https://reports.example.com
+          --ttl-days 30 --max-keep-runs 10
+```
+
+Pytest-driven (plugin):
+
+```yaml
+- run: pytest -q \
+    --allure-bucket $BUCKET \
+    --allure-prefix reports \
+    --allure-project demo \
+    --allure-branch "$GIT_BRANCH" \
+    --allure-cloudfront https://reports.example.com \
+    --allure-ttl-days 30 \
+    --allure-max-keep-runs 10
+```
+
+## Troubleshooting
+
+- Missing Allure binary: ensure the Allure CLI is installed and on PATH.
+- Access denied: verify AWS credentials and bucket IAM for Put/Get/List/Delete.
+- SPA routing 403/404: configure CloudFront error mapping to `/index.html`.
+
+## Development
+
+- Install with Poetry: `poetry install`
+- Run tests: `poetry run pytest -q`
+- Lint (security quick): `poetry run bandit -r pytest_allure_host`
+- Unified lint helper (mirrors CI):
+  ```bash
+  scripts/lint.sh           # check mode (ruff lint+format check, bandit, pip-audit)
+  scripts/lint.sh --fix     # apply ruff fixes + format
+  scripts/lint.sh pre-commit  # also run pre-commit hooks on all files
+  ```
+
+## Quick local trial (macOS)
+
+This section walks you through a minimal end-to-end run locally.
+
+1. Prereqs
+
+- AWS credentials configured (via `AWS_PROFILE` or access keys); set `AWS_REGION`.
+- Allure CLI installed on PATH:
+  ```bash
+  brew install allure
+  ```
+- Python deps installed:
+  ```bash
+  poetry install
+  # or
+  pip install -e .[dev]
+  ```
+
+2. Generate Allure results
+
+- Create a tiny test (optional example):
+  ```bash
+  mkdir -p tests
+  cat > tests/test_sample.py <<'PY'
+  def test_ok():
+      assert True
+  PY
+  ```
+- Run pytest to emit results:
+  ```bash
+  poetry run pytest --alluredir=allure-results
+  ```
+
+3. Preflight and dry-run
+
+```bash
+poetry run publish-allure \
+  --bucket <bucket> \
+  --prefix reports \
+  --project demo \
+  --branch $(git rev-parse --abbrev-ref HEAD) \
+  --cloudfront https://<cloudfront_domain> \
+  --check \
+  --dry-run
+```
+
+4. Publish
+
+```bash
+poetry run publish-allure \
+  --bucket <bucket> \
+  --prefix reports \
+  --project demo \
+  --branch $(git rev-parse --abbrev-ref HEAD) \
+  --cloudfront https://<cloudfront_domain> \
+  --ttl-days 30 \
+  --max-keep-runs 5
+```
+
+5. Verify
+
+- S3: `reports/demo/<branch>/<run_id>/...` and `reports/demo/<branch>/latest/` with `LATEST_READY`.
+- CDN: open printed `run_url` / `latest_url`.
+

pytest_allure_host-0.1.1/README.md

@@ -0,0 +1,275 @@
+# pytest-allure-host
+
+![CI](https://github.com/darrenrabbs/allurehosting/actions/workflows/ci.yml/badge.svg)
+![CodeQL](https://github.com/darrenrabbs/allurehosting/actions/workflows/codeql.yml/badge.svg)
+![PyPI - Version](https://img.shields.io/pypi/v/pytest-allure-host.svg)
+![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)
+
+Publish Allure static reports to private S3 behind CloudFront with history preservation and SPA-friendly routing.
+
+See `docs/architecture.md` and `.github/copilot-instructions.md` for architecture and design constraints.
+
+## Features
+
+- Generate Allure static report from `allure-results`
+- Preserve history by pulling `latest/history` before generation
+- Upload to S3 under `<project>/<branch>/<run_id>/` and update `<project>/<branch>/latest/`
+- Two-phase latest update: upload to `latest_tmp/`, swap into `latest/`, write `LATEST_READY` marker
+- Optional retention: keep only N newest runs (`--max-keep-runs`)
+- Correct caching headers: `index.html` and `widgets/` → `no-cache`; assets → immutable
+- Optional TTL tagging on objects (`--ttl-days`) for S3 lifecycle policies
+- Optional summary JSON output for CI
+- Best-effort manifest at `runs/index.json` with new run metadata
+- Lightweight pointer file `latest.json` (branch root)
+- Human-friendly HTML index at `runs/index.html` for navigating past runs
+  - Columns: Run ID, raw epoch, UTC Time (human readable), Size (pretty units), P/F/B (passed/failed/broken counts), links to the immutable run and the moving latest
+  - Newest run highlighted with a star (★) and soft background
+
+## Requirements
+
+- Python 3.9+
+- AWS credentials with S3 access to the target bucket
+- Allure commandline available on PATH (e.g., via Allure CLI or allure-pytest)
+
+## S3 layout and caching
+
+- Keys:
+  - `s3://<bucket>/<prefix>/<project>/<branch>/<run_id>/...`
+  - `s3://<bucket>/<prefix>/<project>/<branch>/latest/...`
+  - `s3://<bucket>/<prefix>/<project>/<branch>/runs/index.json` (manifest)
+  - `s3://<bucket>/<prefix>/<project>/<branch>/runs/index.html` (HTML index)
+  - `s3://<bucket>/<prefix>/<project>/<branch>/latest.json` (pointer)
+- Two-phase swap writes a `LATEST_READY` marker file under `latest/` when ready.
+- Cache-Control:
+  - `index.html`: `no-cache`
+  - files under `widgets/`: `no-cache`
+  - everything else: `public, max-age=31536000, immutable`
+
+## CLI usage
+
+Install locally for development:
+
+```bash
+pip install -e .[dev]
+```
+
+Run the publisher after tests generate `allure-results`:
+
+```bash
+publish-allure \
+  --bucket your-bucket \
+  --prefix reports \
+  --project demo \
+  --branch main \
+  --cloudfront https://reports.example.com \
+  --ttl-days 30 \
+  --max-keep-runs 10
+```
+
+Flags (CLI):
+
+- `--bucket` (required): S3 bucket name
+- `--prefix` (default: `reports`): Root prefix
+- `--project` (required): Project name
+- `--branch` (default: `$GIT_BRANCH` or `main`)
+- `--run-id` (default: `$ALLURE_RUN_ID` or `YYYYMMDD-HHMMSS`)
+- `--cloudfront` (optional; default: `$ALLURE_CLOUDFRONT`)
+- `--results` (default: `allure-results`): Input directory
+- `--report` (default: `allure-report`): Output directory
+- `--ttl-days` (optional): Add `ttl-days=<N>` object tag
+- `--max-keep-runs` (optional): Keep N newest run prefixes, delete older
+- `--summary-json <path>`: Write machine-readable summary
+- `--check`: Preflight validation (AWS access, allure, inputs)
+- `--dry-run`: Print planned prefixes and sample headers, no upload
+- `--s3-endpoint`: Custom S3 endpoint (e.g. `http://localhost:4566` for LocalStack)
+
+Environment fallbacks:
+
+- `GIT_BRANCH` → `--branch` default
+- `ALLURE_RUN_ID` → `--run-id` default
+- `ALLURE_CLOUDFRONT` → `--cloudfront` default
+- `ALLURE_S3_ENDPOINT` → `--s3-endpoint` default (LocalStack / custom S3)
+
+## Pytest plugin usage
+
+Run tests and publish during terminal summary:
+
+```bash
+pytest \
+  --allure-bucket your-bucket \
+  --allure-prefix reports \
+  --allure-project demo \
+  --allure-branch main \
+  --allure-cloudfront https://reports.example.com \
+  --allure-ttl-days 30 \
+  --allure-max-keep-runs 10
+```
+
+Flags (pytest):
+
+- `--allure-bucket` (required)
+- `--allure-prefix` (default: `reports`)
+- `--allure-project` (required)
+- `--allure-branch` (default: `$GIT_BRANCH` or `main`)
+- `--allure-run-id` (default: `$ALLURE_RUN_ID` or `YYYYMMDD-HHMMSS`)
+- `--allure-cloudfront` (optional; default: `$ALLURE_CLOUDFRONT`)
+- `--allure-ttl-days` (optional)
+- `--allure-max-keep-runs` (optional)
+- `--allure-summary-json <path>` (optional)
+- `--allure-check` / `--allure-dry-run` (optional)
+
+## Preflight and dry-run
+
+- `--check`/`--allure-check` verifies:
+  - S3 bucket reachability (HeadBucket/List)
+  - `allure-results` exists and is non-empty
+  - Allure CLI exists on PATH
+- `--dry-run`/`--allure-dry-run` prints planned prefixes and sample headers; no uploads occur.
+
+## Outputs
+
+- S3 prefixes: run and latest
+- Optional CDN URLs (if `--cloudfront` provided)
+- `runs/index.json` manifest updated with new run entry
+- `runs/index.html` HTML table of recent runs (newest first) with columns: Run ID, Epoch, UTC Time, Size, P/F/B, Run, Latest (newest row highlighted with ★)
+- `latest.json` pointer to current run (simple machine-readable metadata)
+- Optional `--summary-json` with sizes, file counts, and destination URLs
+- `latest/LATEST_READY` marker indicates the swap is complete
+
+## Security
+
+See `SECURITY.md` for how to report vulnerabilities. Never open a public issue containing sensitive details.
+
+## Badges / Status
+
+- CI: multi-version test matrix + lint/security
+- CodeQL: static code analysis
+
+## Contributing
+
+See `CONTRIBUTING.md` and follow the pre-commit hooks (`pre-commit install`).
+
+## Release
+
+Tagged versions (`vX.Y.Z`) are published to PyPI automatically via GitHub OIDC.
+
+## CI examples
+
+GitHub Actions (CLI):
+
+```yaml
+jobs:
+  tests:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.11" }
+      - run: pip install .[dev]
+      - run: pytest -q
+      - name: Publish Allure
+        env:
+          AWS_REGION: us-east-1
+          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+          GIT_BRANCH: ${{ github.ref_name }}
+        run: >-
+          publish-allure --bucket $BUCKET --prefix reports --project demo
+          --branch "$GIT_BRANCH" --cloudfront https://reports.example.com
+          --ttl-days 30 --max-keep-runs 10
+```
+
+Pytest-driven (plugin):
+
+```yaml
+- run: pytest -q \
+    --allure-bucket $BUCKET \
+    --allure-prefix reports \
+    --allure-project demo \
+    --allure-branch "$GIT_BRANCH" \
+    --allure-cloudfront https://reports.example.com \
+    --allure-ttl-days 30 \
+    --allure-max-keep-runs 10
+```
+
+## Troubleshooting
+
+- Missing Allure binary: ensure the Allure CLI is installed and on PATH.
+- Access denied: verify AWS credentials and bucket IAM for Put/Get/List/Delete.
+- SPA routing 403/404: configure CloudFront error mapping to `/index.html`.
+
+## Development
+
+- Install with Poetry: `poetry install`
+- Run tests: `poetry run pytest -q`
+- Lint (security quick): `poetry run bandit -r pytest_allure_host`
+- Unified lint helper (mirrors CI):
+  ```bash
+  scripts/lint.sh           # check mode (ruff lint+format check, bandit, pip-audit)
+  scripts/lint.sh --fix     # apply ruff fixes + format
+  scripts/lint.sh pre-commit  # also run pre-commit hooks on all files
+  ```
+
+## Quick local trial (macOS)
+
+This section walks you through a minimal end-to-end run locally.
+
+1. Prereqs
+
+- AWS credentials configured (via `AWS_PROFILE` or access keys); set `AWS_REGION`.
+- Allure CLI installed on PATH:
+  ```bash
+  brew install allure
+  ```
+- Python deps installed:
+  ```bash
+  poetry install
+  # or
+  pip install -e .[dev]
+  ```
+
+2. Generate Allure results
+
+- Create a tiny test (optional example):
+  ```bash
+  mkdir -p tests
+  cat > tests/test_sample.py <<'PY'
+  def test_ok():
+      assert True
+  PY
+  ```
+- Run pytest to emit results:
+  ```bash
+  poetry run pytest --alluredir=allure-results
+  ```
+
+3. Preflight and dry-run
+
+```bash
+poetry run publish-allure \
+  --bucket <bucket> \
+  --prefix reports \
+  --project demo \
+  --branch $(git rev-parse --abbrev-ref HEAD) \
+  --cloudfront https://<cloudfront_domain> \
+  --check \
+  --dry-run
+```
+
+4. Publish
+
+```bash
+poetry run publish-allure \
+  --bucket <bucket> \
+  --prefix reports \
+  --project demo \
+  --branch $(git rev-parse --abbrev-ref HEAD) \
+  --cloudfront https://<cloudfront_domain> \
+  --ttl-days 30 \
+  --max-keep-runs 5
+```
+
+5. Verify
+
+- S3: `reports/demo/<branch>/<run_id>/...` and `reports/demo/<branch>/latest/` with `LATEST_READY`.
+- CDN: open printed `run_url` / `latest_url`.

pytest_allure_host-0.1.1/pyproject.toml

@@ -0,0 +1,93 @@
+[build-system]
+requires = ["poetry-core>=1.9.0"]
+build-backend = "poetry.core.masonry.api"
+
+[project]
+name = "pytest-allure-host"
+version = "0.1.1"
+description = "Publish Allure static reports to private S3 behind CloudFront with history preservation"
+readme = "README.md"
+license = "MIT"
+authors = [ { name = "Allure Hosting Maintainers" } ]
+requires-python = ">=3.9,<4.0"
+keywords = ["allure", "pytest", "aws", "s3", "cloudfront", "reporting"]
+classifiers = [
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.9",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Intended Audience :: Developers",
+    "Topic :: Software Development :: Testing",
+    "Framework :: Pytest",
+    "Development Status :: 3 - Alpha",
+    "Operating System :: OS Independent"
+]
+
+dependencies = [
+	"boto3>=1.28,<2.0",
+	"PyYAML>=6,<7"
+]
+
+[project.optional-dependencies]
+# (Reserved for runtime extras; dev tooling now uses a Poetry dependency group below.)
+
+[tool.poetry.group.dev]
+optional = true
+
+[tool.poetry.group.dev.dependencies]
+pytest = ">=7,<9"
+moto = {version = ">=5,<6", extras=["s3"]}
+bandit = ">=1.7,<2.0"
+allure-pytest = ">=2,<3"
+pytest-cov = ">=4,<5"
+ruff = ">=0.5,<1.0"
+pip-audit = ">=2.7,<3.0"
+black = ">=24,<25"
+
+[project.scripts]
+publish-allure = "pytest_allure_host.cli:main"
+
+[project.entry-points."pytest11"]
+pytest_allure_host = "pytest_allure_host.plugin"
+
+[project.urls]
+Homepage = "https://github.com/darrenrabbs/allurehosting"
+Repository = "https://github.com/darrenrabbs/allurehosting"
+Documentation = "https://github.com/darrenrabbs/allurehosting#readme"
+"Bug Tracker" = "https://github.com/darrenrabbs/allurehosting/issues"
+Changelog = "https://github.com/darrenrabbs/allurehosting/releases"
+
+# Package include (PEP 621 doesn't specify this; still handled by Poetry configuration)
+[tool.poetry]
+packages = [{ include = "pytest_allure_host" }]
+# PEP 621 is authoritative; legacy duplicate metadata removed (require Poetry 2.2.1+)
+
+[tool.poetry.dependencies]
+# Retained only for Poetry's internal processing of the runtime dependency group.
+python = ">=3.9,<4.0"
+
+
+[tool.ruff]
+line-length = 100
+target-version = "py39"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "B", "UP", "S", "W", "C90"]
+ignore = ["E203", "E501"]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/**" = ["S101"]  # allow bare asserts in test modules
+
+[tool.ruff.format]
+quote-style = "double"
+indent-style = "space"
+skip-magic-trailing-comma = false
+line-ending = "lf"
+
+[tool.black]
+line-length = 100
+target-version = ["py39"]
+skip-string-normalization = false
+color = true

pytest_allure_host-0.1.1/pytest_allure_host/__init__.py

@@ -0,0 +1,6 @@
+from .utils import PublishConfig, default_run_id  # re-export key types
+
+__all__ = [
+    "PublishConfig",
+    "default_run_id",
+]