Merge pull request #63 from mgaitan/agent/workspace-packages

Finalize workspace package names and publishing

Author: mgaitan

.github/workflows/cd.yml

@@ -10,7 +10,7 @@ on:
       - "packages/**"
       - "src/**"
       - "README.md"
-      - ".github/workflows/ci.yml"
+      - ".github/workflows/**"
   push:
     branches:
       - main
@@ -20,7 +20,7 @@ on:
       - "packages/**"
       - "src/**"
       - "README.md"
-      - ".github/workflows/ci.yml"
+      - ".github/workflows/**"
 
 permissions:
   contents: read

.github/workflows/ci.yml

@@ -0,0 +1,51 @@
+name: Publish markdown-this
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "Version already written in packages/markdown-this/pyproject.toml"
+        required: true
+        type: string
+
+permissions:
+  contents: read
+  id-token: write
+
+jobs:
+  publish:
+    name: Publish markdown-this
+    runs-on: ubuntu-latest
+    if: github.event_name == 'workflow_dispatch' || startsWith(github.event.release.tag_name, 'markdown-this-v')
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@v7
+
+      - name: Verify package version
+        env:
+          RELEASE_TAG: ${{ github.event.release.tag_name }}
+          INPUT_VERSION: ${{ inputs.version }}
+        run: |
+          version="$(uv version --package markdown-this --short)"
+          if [ "${{ github.event_name }}" = "release" ]; then
+            expected="${RELEASE_TAG#markdown-this-v}"
+          else
+            expected="$INPUT_VERSION"
+          fi
+          test "$version" = "$expected" || {
+            echo "pyproject version ($version) does not match release version ($expected)"
+            exit 1
+          }
+
+      - name: Build package
+        run: uv build --package markdown-this --out-dir dist/markdown-this
+
+      - name: Publish to PyPI
+        run: uv publish dist/markdown-this/*

.github/workflows/publish-markdown-this.yml

@@ -0,0 +1,51 @@
+name: Publish md-to-telegraph
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "Version already written in packages/md-to-telegraph/pyproject.toml"
+        required: true
+        type: string
+
+permissions:
+  contents: read
+  id-token: write
+
+jobs:
+  publish:
+    name: Publish md-to-telegraph
+    runs-on: ubuntu-latest
+    if: github.event_name == 'workflow_dispatch' || startsWith(github.event.release.tag_name, 'md-to-telegraph-v')
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@v7
+
+      - name: Verify package version
+        env:
+          RELEASE_TAG: ${{ github.event.release.tag_name }}
+          INPUT_VERSION: ${{ inputs.version }}
+        run: |
+          version="$(uv version --package md-to-telegraph --short)"
+          if [ "${{ github.event_name }}" = "release" ]; then
+            expected="${RELEASE_TAG#md-to-telegraph-v}"
+          else
+            expected="$INPUT_VERSION"
+          fi
+          test "$version" = "$expected" || {
+            echo "pyproject version ($version) does not match release version ($expected)"
+            exit 1
+          }
+
+      - name: Build package
+        run: uv build --package md-to-telegraph --out-dir dist/md-to-telegraph
+
+      - name: Publish to PyPI
+        run: uv publish dist/md-to-telegraph/*

.github/workflows/publish-md-to-telegraph.yml

@@ -1,18 +1,18 @@
 # Working with This Workspace
 
-Lobstergram is a uv-managed Python workspace. Keep changes small, preserve the
+Lobstersgram is a uv-managed Python workspace. Keep changes small, preserve the
 boundaries between the application and reusable packages, and run the checks
 that cover the code you touched.
 
 This file is adapted from the [python-package-copier-template AGENTS.md](https://github.com/mgaitan/python-package-copier-template/blob/main/AGENTS.md).
 
 ## Workspace Layout
 
-- `src/lobstergram/` contains the main Telegram application and its
-  `lobstergram` command-line entrypoint.
+- `src/lobstersgram/` contains the main Telegram application and its
+  `lobstersgram` command-line entrypoint.
 - `packages/md-to-telegraph/` contains the reusable Markdown-to-Telegraph
   package.
-- `packages/url-to-markdown/` contains the reusable URL/HTML-to-Markdown
+- `packages/markdown-this/` contains the reusable URL/HTML-to-Markdown
   package.
 - Each child package has its own `pyproject.toml`, metadata, dependencies,
   version, `README.md`, `src/<import_name>/`, and package-local tests.
@@ -25,24 +25,24 @@ This file is adapted from the [python-package-copier-template AGENTS.md](https:/
 
 ```bash
 uv sync
-uv run lobstergram --help
+uv run lobstersgram --help
 uv run pytest -q
-uv run pytest packages/url-to-markdown/tests/test_html.py
+uv run pytest packages/markdown-this/tests/test_html.py
 uv run ruff check .
 uv run ruff format --check .
 uv build --all-packages
 ```
 
-The default coverage gate measures `md_to_telegraph` and `url_to_markdown` at
+The default coverage gate measures `md_to_telegraph` and `markdown_this` at
 100%. The application tests run in the same pytest invocation, but the root
-configuration does not currently enforce 100% coverage for `lobstergram`.
+configuration does not currently enforce 100% coverage for `lobstersgram`.
 
 ## Package Boundaries
 
 - Keep Telegram orchestration, configuration, persistence, and runtime state
-  in `src/lobstergram/`.
+  in `src/lobstersgram/`.
 - Keep reusable conversion and extraction logic in the relevant child package.
-- Reusable packages should not import application modules from `lobstergram`.
+- Reusable packages should not import application modules from `lobstersgram`.
 - Put shared QA configuration in the root `pyproject.toml`; keep package
   metadata and package-specific runtime dependencies in the child package's
   `pyproject.toml`.
@@ -53,15 +53,17 @@ Packages are versioned and released independently. Bump a package from the
 workspace root, for example:
 
 ```bash
-uv version --package url-to-markdown --bump patch
+uv version --package markdown-this --bump patch
 uv lock
-git tag url-to-markdown-v<version>
-git push origin url-to-markdown-v<version>
+git tag markdown-this-v<version>
+git push origin markdown-this-v<version>
 ```
 
-Use the package names `lobstergram`, `md-to-telegraph`, or
-`url-to-markdown`. The `cd.yml` workflow builds and publishes only the package
-selected by its tag.
+The reusable packages are published independently. Each publishing workflow
+is dedicated to one package: `publish-md-to-telegraph.yml` publishes
+`md-to-telegraph`, and `publish-markdown-this.yml` publishes `markdown-this`.
+The `lobstersgram` application is not published to PyPI yet. A release tag only
+activates the matching workflow.
 
 ## Editing and Verification
 

AGENTS.md

@@ -1,8 +1,8 @@
-# Lobstergram: Lobsters → Telegraph → Telegram (Serverless)
+# Lobstersgram: Lobsters → Telegraph → Telegram (Serverless)
 
 [![CI](https://github.com/mgaitan/lobstersgram/actions/workflows/ci.yml/badge.svg)](https://github.com/mgaitan/lobstersgram/actions/workflows/ci.yml)
 
-Lobstergram is a fast Telegram client for [lobste.rs](https://lobste.rs). It delivers the hottest Lobsters stories (articles that reached the home page) right into Telegram with a clean telegra.ph reading view.
+Lobstersgram is a fast Telegram client for [lobste.rs](https://lobste.rs). It delivers the hottest Lobsters stories (articles that reached the home page) right into Telegram with a clean telegra.ph reading view.
 
 Bot: [@lobstersgram_bot](https://t.me/lobstersgram_bot)
 Post: https://mgaitan.github.io/en/posts/lobstersgram-cliente-rapido-lobsters/
@@ -13,7 +13,7 @@ Commands:
 
 Demo:
 
-[![Lobstergram demo](https://img.youtube.com/vi/wdzIBFYjJ3Y/hqdefault.jpg)](https://youtube.com/shorts/wdzIBFYjJ3Y?si=yMhLPjz7kDGX_1Wl)
+[![Lobstersgram demo](https://img.youtube.com/vi/wdzIBFYjJ3Y/hqdefault.jpg)](https://youtube.com/shorts/wdzIBFYjJ3Y?si=yMhLPjz7kDGX_1Wl)
 
 ---
 
@@ -40,28 +40,33 @@ No callbacks, no pagination logic, no bot process running 24/7.
 
 This workspace contains two reusable packages used by the bot:
 
-- [`url-to-markdown`](packages/url-to-markdown/README.md): extracts web pages and supported special URLs as Markdown.
+- [`markdown-this`](packages/markdown-this/README.md): extracts web pages and supported special URLs as Markdown.
 - [`md-to-telegraph`](packages/md-to-telegraph/README.md): converts Markdown into Telegraph DOM nodes.
 
 Each package has its own version and can be released independently from this workspace.
 
 ### Independent releases
 
 Versions live in each package's own `pyproject.toml`. For example, to bump and
-release `url-to-markdown`:
+release `markdown-this`:
 
 ```bash
-uv version --package url-to-markdown --bump patch
+uv version --package markdown-this --bump patch
 uv lock
-git commit -am "Release url-to-markdown $(uv version --package url-to-markdown --short)"
-git tag "url-to-markdown-v$(uv version --package url-to-markdown --short)"
+git commit -am "Release markdown-this $(uv version --package markdown-this --short)"
+git tag "markdown-this-v$(uv version --package markdown-this --short)"
 git push origin main --tags
 ```
 
-Create the GitHub release from that tag. The `cd.yml` workflow verifies the
-matching package version, builds only that package, and publishes it to PyPI.
-Use the same commands with `md-to-telegraph` or `lobstergram` as the package
-name. The tag format is `<package>-v<version>`.
+Create the GitHub release from that tag. The matching publishing workflow
+verifies the package version, builds only that package, and publishes it to
+PyPI. The reusable packages have separate Trusted Publisher workflows:
+`publish-md-to-telegraph.yml` publishes `md-to-telegraph`, and
+`publish-markdown-this.yml` publishes `markdown-this`. The `lobstersgram`
+application is not published to PyPI yet.
+
+Use the same commands with `md-to-telegraph` as the package name. The tag
+format is `<package>-v<version>`.
 
 ---
 
@@ -107,7 +112,7 @@ All secrets are stored securely in GitHub Actions.
 
 To register subscribers:
 - Send `/start` to the bot from the Telegram account or group you want to receive posts.
-- Run the workflow once (or run `uv run lobstergram --read-messages`) to record the
+- Run the workflow once (or run `uv run lobstersgram --read-messages`) to record the
   `chat_id` values into `subscribers.json`.
 
 For local development, you can set `TELEGRAM_DEV_CHAT_ID` to force all sends

README.md

@@ -1,6 +1,6 @@
-# url-to-markdown
+# markdown-this
 
-[![PyPI](https://img.shields.io/pypi/v/url-to-markdown)](https://pypi.org/project/url-to-markdown/)
+[![PyPI](https://img.shields.io/pypi/v/markdown-this)](https://pypi.org/project/markdown-this/)
 
 Extract the readable content of a URL and convert it to Markdown. The package
 also handles GitHub repositories and Markdown files through the GitHub API,
@@ -9,13 +9,13 @@ and arXiv abstract pages through their HTML representation.
 ## Installation
 
 ```bash
-uv add url-to-markdown
+uv add markdown-this
 ```
 
 ## Usage
 
 ```python
-from url_to_markdown import extract_main_content
+from markdown_this import extract_main_content
 
 title, markdown, fallback_text, intro = extract_main_content(
     "https://example.com/article"
@@ -31,8 +31,8 @@ package modules when an application needs more control over the pipeline.
 ## Development
 
 ```bash
-uv run pytest packages/url-to-markdown/tests
-uv run ruff check packages/url-to-markdown
+uv run pytest packages/markdown-this/tests
+uv run ruff check packages/markdown-this
 ```
 
 ## License