fix(repo): update repo naming

Author: jharrell

.github/workflows/publish-pypi.yml

@@ -1,6 +1,6 @@
 # This workflow is triggered when a GitHub release is created.
 # It can also be run manually to re-publish to PyPI in case it failed for some reason.
-# You can run this workflow by navigating to https://www.github.com/replicate/replicate-python-stainless/actions/workflows/publish-pypi.yml
+# You can run this workflow by navigating to https://www.github.com/replicate/replicate-python-beta/actions/workflows/publish-pypi.yml
 name: Publish PyPI
 on:
   workflow_dispatch:

.github/workflows/release-doctor.yml

@@ -9,7 +9,7 @@ jobs:
   release_doctor:
     name: release doctor
     runs-on: ubuntu-latest
-    if: github.repository == 'replicate/replicate-python-stainless' && (github.event_name == 'push' || github.event_name == 'workflow_dispatch' || startsWith(github.head_ref, 'release-please') || github.head_ref == 'next')
+    if: github.repository == 'replicate/replicate-python-beta' && (github.event_name == 'push' || github.event_name == 'workflow_dispatch' || startsWith(github.head_ref, 'release-please') || github.head_ref == 'next')
 
     steps:
       - uses: actions/checkout@v4

README.md

@@ -417,9 +417,9 @@ prediction = response.parse()  # get the object that `predictions.create()` woul
 print(prediction.id)
 ```
 
-These methods return an [`APIResponse`](https://github.com/replicate/replicate-python-stainless/tree/main/src/replicate/_response.py) object.
+These methods return an [`APIResponse`](https://github.com/replicate/replicate-python-beta/tree/main/src/replicate/_response.py) object.
 
-The async client returns an [`AsyncAPIResponse`](https://github.com/replicate/replicate-python-stainless/tree/main/src/replicate/_response.py) with the same structure, the only difference being `await`able methods for reading the response content.
+The async client returns an [`AsyncAPIResponse`](https://github.com/replicate/replicate-python-beta/tree/main/src/replicate/_response.py) with the same structure, the only difference being `await`able methods for reading the response content.
 
 #### `.with_streaming_response`
 

pyproject.toml

@@ -36,8 +36,8 @@ classifiers = [
 ]
 
 [project.urls]
-Homepage = "https://github.com/replicate/replicate-python-stainless"
-Repository = "https://github.com/replicate/replicate-python-stainless"
+Homepage = "https://github.com/replicate/replicate-python-beta"
+Repository = "https://github.com/replicate/replicate-python-beta"
 
 [project.optional-dependencies]
 aiohttp = ["aiohttp", "httpx_aiohttp>=0.1.8"]
@@ -125,7 +125,7 @@ path = "README.md"
 [[tool.hatch.metadata.hooks.fancy-pypi-readme.substitutions]]
 # replace relative links with absolute links
 pattern = '\[(.+?)\]\(((?!https?://)\S+?)\)'
-replacement = '[\1](https://github.com/replicate/replicate-python-stainless/tree/main/\g<2>)'
+replacement = '[\1](https://github.com/replicate/replicate-python-beta/tree/main/\g<2>)'
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]

src/replicate/_files.py

@@ -34,7 +34,7 @@ def assert_is_file_content(obj: object, *, key: str | None = None) -> None:
     if not is_file_content(obj):
         prefix = f"Expected entry at `{key}`" if key is not None else f"Expected file input `{obj!r}`"
         raise RuntimeError(
-            f"{prefix} to be bytes, an io.IOBase instance, PathLike or a tuple but received {type(obj)} instead. See https://github.com/replicate/replicate-python-stainless/tree/main#file-uploads"
+            f"{prefix} to be bytes, an io.IOBase instance, PathLike or a tuple but received {type(obj)} instead. See https://github.com/replicate/replicate-python-beta/tree/main#file-uploads"
         ) from None