add cargo package publish GA and update readme

Author: Kanishk2207

.github/workflows/publish-crate.yml

@@ -0,0 +1,77 @@
+name: Publish Crate
+
+on:
+  workflow_dispatch:
+    inputs:
+      dry_run:
+        description: "Run cargo publish --dry-run (recommended first)"
+        required: true
+        default: true
+        type: boolean
+      expected_tag:
+        description: "Optional tag to validate against Cargo.toml version (example: v0.1.0)"
+        required: false
+        type: string
+
+permissions:
+  contents: read
+
+concurrency:
+  group: publish-crate-${{ github.ref }}
+  cancel-in-progress: false
+
+jobs:
+  publish:
+    name: Publish to crates.io
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Set up Rust
+        uses: dtolnay/rust-toolchain@stable
+
+      - name: Cache cargo artifacts
+        uses: Swatinem/rust-cache@v2
+
+      - name: Read package metadata
+        id: meta
+        shell: bash
+        run: |
+          PKGID="$(cargo pkgid)"
+          PACKAGE_NAME="$(echo "$PKGID" | sed -E 's/.*#([^@]+)@.*/\1/')"
+          PACKAGE_VERSION="$(echo "$PKGID" | sed -E 's/.*@([^ ]+)$/\1/')"
+
+          echo "package_name=$PACKAGE_NAME" >> "$GITHUB_OUTPUT"
+          echo "package_version=$PACKAGE_VERSION" >> "$GITHUB_OUTPUT"
+
+          echo "Publishing target: $PACKAGE_NAME@$PACKAGE_VERSION"
+
+      - name: Validate expected tag
+        if: inputs.expected_tag != ''
+        shell: bash
+        run: |
+          EXPECTED="v${{ steps.meta.outputs.package_version }}"
+          PROVIDED="${{ inputs.expected_tag }}"
+          if [ "$EXPECTED" != "$PROVIDED" ]; then
+            echo "::error::Tag mismatch. Provided '$PROVIDED' but Cargo.toml expects '$EXPECTED'."
+            exit 1
+          fi
+
+      - name: Dry run publish
+        if: inputs.dry_run
+        run: cargo publish --dry-run
+
+      - name: Publish
+        if: ${{ !inputs.dry_run }}
+        env:
+          CRATES_IO_TOKEN: ${{ secrets.CRATES_IO_TOKEN }}
+        shell: bash
+        run: |
+          if [ -z "$CRATES_IO_TOKEN" ]; then
+            echo "::error::Missing CRATES_IO_TOKEN repository secret."
+            exit 1
+          fi
+          cargo publish --token "$CRATES_IO_TOKEN"

CONTRIBUTING.md

@@ -61,6 +61,8 @@ cargo test
 `filo` follows SemVer and uses the package version in `Cargo.toml` as the source of truth.
 
 - `Cargo.toml` `[package].version` is the crate/app version.
+- crates.io package name is `filo-rs`.
+- Installed CLI command remains `filo`.
 - `filo --version` comes from that same Cargo package version.
 - Release tags should match the package version with a leading `v`.
 
@@ -77,6 +79,17 @@ Suggested release flow:
 4. Bump/finalize version to `X.Y.Z` (without prerelease suffix) if needed.
 5. Tag `main` with `vX.Y.Z` and push the tag. GitHub will publish a stable release.
 
+## Publishing to crates.io
+
+- Use the dedicated `Publish Crate` workflow (manual trigger) instead of coupling crate publish to the tag release workflow.
+- Add `CRATES_IO_TOKEN` in repository secrets before first publish.
+- Run a dry run first, then run a real publish.
+
+Why separate workflows?
+
+- GitHub Release creation and crates.io publishing have different failure/retry behavior.
+- `cargo publish` is immutable per version; separating it reduces accidental publishes.
+
 ## Pull Request Checklist
 
 - [ ] Code is formatted (`cargo fmt --check`)

readme.md

@@ -58,6 +58,14 @@ that's the point.
 
 ## Installation
 
+### From crates.io (recommended)
+
+```bash
+cargo install filo-rs
+```
+
+The package name is `filo-rs`, and the installed command is still `filo`.
+
 ### From source
 
 Requires Rust `1.85` or newer.