handle publish with GH CI

Author: joeworkman

.github/workflows/release.yml

@@ -191,5 +191,91 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
-  # Publishing to crates.io, npm, PyPI, and RubyGems is handled locally
-  # via bin/publish.sh after the release workflow completes.
+  publish-crates:
+    name: Publish to crates.io
+    needs: [release]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install Rust toolchain
+        uses: dtolnay/rust-toolchain@stable
+
+      - name: Publish inky-core
+        run: cargo publish -p inky-core
+        env:
+          CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
+
+      - name: Publish inky-cli
+        run: cargo publish -p inky-cli
+        env:
+          CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
+
+  publish-npm:
+    name: Publish to npm
+    needs: [release]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/setup-node@v4
+        with:
+          registry-url: https://registry.npmjs.org
+
+      - name: Download WASM artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: wasm-nodejs
+          path: .
+
+      - name: Extract and publish
+        run: |
+          tar xzf inky-wasm-nodejs.tar.gz
+          cd node
+          VERSION=$(node -p "require('./package.json').version")
+          if echo "$VERSION" | grep -qE '(alpha|beta|rc|dev)'; then
+            npm publish --access public --tag beta
+          else
+            npm publish --access public
+          fi
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+  publish-pypi:
+    name: Publish to PyPI
+    needs: [release]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.x'
+
+      - name: Build and publish
+        run: |
+          pip install build twine
+          cd bindings/python
+          python -m build
+          twine upload dist/*
+        env:
+          TWINE_USERNAME: __token__
+          TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
+
+  publish-rubygems:
+    name: Publish to RubyGems
+    needs: [release]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.3'
+
+      - name: Build and publish
+        run: |
+          cd bindings/ruby
+          gem build inky-email.gemspec
+          GEM_FILE=$(ls inky-email-*.gem | head -1)
+          gem push "$GEM_FILE"
+        env:
+          GEM_HOST_API_KEY: ${{ secrets.RUBYGEMS_API_KEY }}

bin/release.sh

@@ -169,11 +169,10 @@ else
     echo "Warning: inky-go repo not found at ../inky-go — skipping Go module tag."
 fi
 
-# Publish to package registries
-echo ""
-read -r -p "==> Publish to package registries now? [y/N] " response
-if [[ "$response" =~ ^[Yy]$ ]]; then
-    bin/publish.sh
-fi
+# Publishing to crates.io, npm, PyPI, and RubyGems is handled by the
+# release workflow in CI. If any publish step fails, use bin/publish.sh
+# as a manual fallback.
 
 echo "==> Done! Inky $TAG has been released."
+echo "    Publishing to registries will happen automatically via CI."
+echo "    If needed, run bin/publish.sh as a fallback."