Rename package from hypersync-temp back to hypersync for PyPI

[JasoonS]

Summary by CodeRabbit

• Documentation

  • Removed temporary package documentation and PyPI installation instructions from README.

• Chores

  • Transitioned package name from hypersync-temp to hypersync. Users should reinstall using the official package name.
  • Enhanced GitHub Actions workflow configuration with improved PyPI authentication for publishing releases.

[coderabbitai]

📝 Walkthrough

Walkthrough

The package name is consolidated from the temporary hypersync-temp to the final hypersync across configuration and documentation. The publishing workflow is updated to use OIDC token authentication instead of API token-based secrets.

Changes

Cohort / File(s)	Summary
Package metadata pyproject.toml	Updated project name from hypersync-temp to hypersync.
Publishing workflow .github/workflows/publish.yml	Added id-token: write permission and removed MATURIN_PYPI_TOKEN environment variable, transitioning to OIDC token authentication for PyPI uploads.
Documentation README.md	Removed temporary publishing note about hypersync-temp and its installation instructions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Update CI workflow: modernize action versions and runners #52: Reverses earlier temporary rename/publishing changes by updating package metadata back from hypersync-temp to hypersync, removing related documentation, and modifying the publishing workflow.

Poem

🐰 No more temporary names, the time has come to stay,
From hypersync-temp back to hypersync we fly today,
OIDC tokens flutter, no secrets to conceal,
The rabbit's package hops home—finally for real! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: renaming the package from hypersync-temp back to hypersync, which is reflected across pyproject.toml, README.md, and the GitHub Actions workflow configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rename-package-to-hypersync

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[JasoonS]

Waiting for a publish! https://github.com/enviodev/hypersync-client-python/actions/runs/23444557341

[coderabbitai]

🧹 Nitpick comments (1)

.github/workflows/publish.yml (1)

133-143: Consider adding an environment for the release job.

While OIDC trusted publishing will work without an explicit environment, adding one provides an additional layer of security through GitHub's environment protection rules (e.g., required reviewers, deployment branches).

♻️ Optional: Add environment for deployment protection

 release:
   name: Release
   runs-on: ubuntu-latest
+  environment: pypi
   needs: [linux, windows, macos, sdist]
   steps:

This requires configuring a pypi environment in GitHub repository settings and updating the PyPI trusted publisher to reference this environment.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/publish.yml around lines 133 - 143, Add a GitHub Actions
environment to the release job by updating the job named "release" to include an
environment (e.g., environment: pypi) so the job is subject to repository
environment protection rules; update the workflow near the job that calls
PyO3/maturin-action@v1 (the "Publish to PyPI" step) and ensure you have
configured a corresponding "pypi" environment in the repo settings and adjusted
the PyPI trusted publisher to reference that environment.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/workflows/publish.yml:
- Around line 133-143: Add a GitHub Actions environment to the release job by
updating the job named "release" to include an environment (e.g., environment:
pypi) so the job is subject to repository environment protection rules; update
the workflow near the job that calls PyO3/maturin-action@v1 (the "Publish to
PyPI" step) and ensure you have configured a corresponding "pypi" environment in
the repo settings and adjusted the PyPI trusted publisher to reference that
environment.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 05fe4120-ef16-435e-b6c0-857ca578b947

📥 Commits

Reviewing files that changed from the base of the PR and between 6024878 and 0ec710f.

📒 Files selected for processing (3)

• .github/workflows/publish.yml
• README.md
• pyproject.toml

💤 Files with no reviewable changes (1)

• README.md

[JasoonS]

Working - merging