Add automated PyPI publishing workflow

[Copilot]

The package was GitHub-only with no PyPI presence. This adds a CI workflow to build and publish the package to PyPI on every push to main, using OIDC Trusted Publishing (no stored secrets).

Changes

.github/workflows/publish.yml (new)

• build job: builds sdist + wheel via python -m build, uploads as artifact
• publish job: downloads artifact and publishes via pypa/gh-action-pypi-publish, scoped to a pypi GitHub Environment
• Triggers on pushes to main
• Minimal permissions: contents: read globally, id-token: write only on the publish job

pyproject.toml

• Added keywords, classifiers, and [project.urls] (Homepage, Repo, Docs, Bug Tracker) for a richer PyPI listing
• Relaxed numpy and numba version constraints from == to >=

Required setup on your end

1. PyPI Trusted Publisher — go to pypi.org/manage/account/publishing and add a pending publisher:
   • Project: cudakima | Owner: asantini29 | Repo: CudAkima | Workflow: publish.yml | Environment: pypi
2. GitHub Environment — create a pypi environment under Settings → Environments (add approval gates if desired)
3. Version bump — PyPI rejects duplicate versions; bump version in pyproject.toml before each release push

Original prompt

---

This section details on the original issue you should resolve

<issue_title>publish to pypi</issue_title>
<issue_description>The package only lives on github at the moment, so I want to publish it on pypi as well.

Set up the workflow necessary to package and publish to pypi the master branch on push. </issue_description>

<agent_instructions>Prepare everything needed for continuous integration and publishing. prompt me with the required steps on my side</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes publish to pypi #7

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[asantini29]

here I do not have a master branch, but a main. change the workflow to get triggered by changes on main.
also, in the pyprject.toml, change the requirements for both numpy and numba from "==" to ">="

[Copilot]

here I do not have a master branch, but a main. change the workflow to get triggered by changes on main.
also, in the pyprject.toml, change the requirements for both numpy and numba from "==" to ">="

Done in commit 2f999da:

• Workflow now triggers on pushes to main
• numpy and numba requirements changed from == to >= in pyproject.toml