Fix/cargo registry token

[lriesebos]

follow up changes on #28 including tag/version check and cargo variables.

1. added cargo version / tag match check
2. added CARGO_REGISTRY_TOKEN env variable using crates.io trusted publishing

@gz , I did not see any secrets in the settings of this repo. will you add a cargo registry token?

[gz]

hey @lriesebos it should not be needed; I configured the repo for trusted publishing from .github/workflows/publish.yml

https://crates.io/docs/trusted-publishing

so all you need to so is mint the token during the action using the sample from the link, e.g., something like this

name: Publish to crates.io
on:
  push:
    tags: ['v*']  # Triggers when pushing tags starting with 'v'
jobs:
  publish:
    runs-on: ubuntu-latest
    environment: release  # Optional: for enhanced security
    permissions:
      id-token: write     # Required for OIDC token exchange
    steps:
    - uses: actions/checkout@v6
    - uses: rust-lang/crates-io-auth-action@v1
      id: auth
    - run: cargo publish
      env:
        CARGO_REGISTRY_TOKEN: ${{ steps.auth.outputs.token }}

[gz]

looks fine as long as you get the registry token from the action

[lriesebos]

new to publishing to crates.io, so appreciate the help. how about this?

[gz]

lgtm!

[gz]

looks like still some problem but it went furhter this time

https://github.com/gz/rust-uio/actions/runs/27023960269/job/79759025077