osintkit 0.1.1__tar.gz → 0.1.2__tar.gz

{osintkit-0.1.1 → osintkit-0.1.2}/.github/workflows/release.yml

@@ -6,6 +6,7 @@ on:
 
 permissions:
   contents: write
+  actions: write
 
 jobs:
   build:
@@ -34,3 +35,8 @@ jobs:
           files: |
             dist/*
           generate_release_notes: true
+      - name: Trigger PyPI publish
+        if: vars.PUBLISH_TO_PYPI == 'true'
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: gh workflow run publish.yml --ref "${GITHUB_REF_NAME}" --repo "$GITHUB_REPOSITORY"

{osintkit-0.1.1 → osintkit-0.1.2}/CHANGELOG.md

@@ -6,6 +6,13 @@ All notable changes are recorded here. The format follows
 
 ## Unreleased
 
+## 0.1.2 — 2026-11-02
+
+### Fixed
+
+- releases now dispatch the PyPI job explicitly, since `GITHUB_TOKEN` releases do not fire
+  `release` events
+
 ## 0.1.1 — 2026-11-02
 
 ### Added

{osintkit-0.1.1 → osintkit-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: osintkit
-Version: 0.1.1
+Version: 0.1.2
 Summary: Public-data OSINT aggregator for emails, usernames, domains, and companies
 Project-URL: Homepage, https://github.com/sjdsjadjajdjsa/osintkit
 Project-URL: Issues, https://github.com/sjdsjadjajdjsa/osintkit/issues
@@ -34,6 +34,7 @@ Description-Content-Type: text/markdown
 
 [![ci](https://github.com/sjdsjadjajdjsa/osintkit/actions/workflows/ci.yml/badge.svg)](https://github.com/sjdsjadjajdjsa/osintkit/actions/workflows/ci.yml)
 [![python](https://img.shields.io/badge/python-3.12%20%7C%203.13-blue)](pyproject.toml)
+[![pypi](https://img.shields.io/pypi/v/osintkit)](https://pypi.org/project/osintkit/)
 [![license](https://img.shields.io/badge/license-MIT-green)](LICENSE)
 [![ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)
 
@@ -62,14 +63,13 @@ on a domain or company. Findings are leads to verify, not facts.
 ## Install
 
 ```bash
-uv tool install git+https://github.com/sjdsjadjajdjsa/osintkit
+pipx install osintkit
 # or
-pipx install git+https://github.com/sjdsjadjajdjsa/osintkit
+uv tool install osintkit
 ```
 
-[Releases](https://github.com/sjdsjadjajdjsa/osintkit/releases) carry a signed-checksum wheel;
-`pip install osintkit-0.1.0-py3-none-any.whl` works from one. From a clone,
-`pip install -e .` also works. Python 3.12+ only.
+Every [release](https://github.com/sjdsjadjajdjsa/osintkit/releases) also carries a wheel with
+checksums, and `pip install -e .` works from a clone. Python 3.12+ only.
 
 ## Quick start
 

{osintkit-0.1.1 → osintkit-0.1.2}/README.md

@@ -2,6 +2,7 @@
 
 [![ci](https://github.com/sjdsjadjajdjsa/osintkit/actions/workflows/ci.yml/badge.svg)](https://github.com/sjdsjadjajdjsa/osintkit/actions/workflows/ci.yml)
 [![python](https://img.shields.io/badge/python-3.12%20%7C%203.13-blue)](pyproject.toml)
+[![pypi](https://img.shields.io/pypi/v/osintkit)](https://pypi.org/project/osintkit/)
 [![license](https://img.shields.io/badge/license-MIT-green)](LICENSE)
 [![ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)
 
@@ -30,14 +31,13 @@ on a domain or company. Findings are leads to verify, not facts.
 ## Install
 
 ```bash
-uv tool install git+https://github.com/sjdsjadjajdjsa/osintkit
+pipx install osintkit
 # or
-pipx install git+https://github.com/sjdsjadjajdjsa/osintkit
+uv tool install osintkit
 ```
 
-[Releases](https://github.com/sjdsjadjajdjsa/osintkit/releases) carry a signed-checksum wheel;
-`pip install osintkit-0.1.0-py3-none-any.whl` works from one. From a clone,
-`pip install -e .` also works. Python 3.12+ only.
+Every [release](https://github.com/sjdsjadjajdjsa/osintkit/releases) also carries a wheel with
+checksums, and `pip install -e .` works from a clone. Python 3.12+ only.
 
 ## Quick start
 

{osintkit-0.1.1 → osintkit-0.1.2}/docs/REFERENCE.md

@@ -103,10 +103,12 @@ if every collector breaks, so upstream parser rot surfaces without a nightly ful
 
 ## Publishing
 
-`.github/workflows/publish.yml` builds and uploads to PyPI on a published release, using Trusted
-Publishing (OIDC, `pypi` environment, no token). It is inert until you:
+Releases publish to PyPI through Trusted Publishing (OIDC, `pypi` environment, no token).
 
-1. Create the project on PyPI and add a trusted publisher for this repo and the `pypi` environment.
-2. Set the repository variable `PUBLISH_TO_PYPI=true`.
+The chain: `release.yml` builds, attaches assets, then dispatches `publish.yml` when the
+repository variable `PUBLISH_TO_PYPI` is `true`. The dispatch is needed because releases created
+by `GITHUB_TOKEN` do not fire `release` events.
 
-Until then, releases attach wheel and sdist assets to GitHub itself.
+To fail safely, `publish.yml` is skipped unless that variable is set and the PyPI pending
+publisher matches owner `sjdsjadjajdjsa`, repository `osintkit`, workflow `publish.yml`, and
+environment `pypi`.

{osintkit-0.1.1 → osintkit-0.1.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "osintkit"
-version = "0.1.1"
+version = "0.1.2"
 description = "Public-data OSINT aggregator for emails, usernames, domains, and companies"
 readme = "README.md"
 requires-python = ">=3.12"

{osintkit-0.1.1 → osintkit-0.1.2}/src/osintkit/__init__.py

@@ -1,3 +1,3 @@
 """osintkit: a public-data OSINT aggregator."""
 
-__version__ = "0.1.1"
+__version__ = "0.1.2"