pierre-storage 0.12.1__tar.gz → 1.0.1__tar.gz

pierre_storage-1.0.1/LICENSE

@@ -0,0 +1,189 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1.  Definitions.
+
+    "License" shall mean the terms and conditions for use, reproduction, and
+    distribution as defined by Sections 1 through 9 of this document.
+
+    "Licensor" shall mean the copyright owner or entity authorized by the
+    copyright owner that is granting the License.
+
+    "Legal Entity" shall mean the union of the acting entity and all other
+    entities that control, are controlled by, or are under common control with
+    that entity. For the purposes of this definition, "control" means (i) the
+    power, direct or indirect, to cause the direction or management of such
+    entity, whether by contract or otherwise, or (ii) ownership of fifty percent
+    (50%) or more of the outstanding shares, or (iii) beneficial ownership of
+    such entity.
+
+    "You" (or "Your") shall mean an individual or Legal Entity exercising
+    permissions granted by this License.
+
+    "Source" form shall mean the preferred form for making modifications,
+    including but not limited to software source code, documentation source, and
+    configuration files.
+
+    "Object" form shall mean any form resulting from mechanical transformation
+    or translation of a Source form, including but not limited to compiled
+    object code, generated documentation, and conversions to other media types.
+
+    "Work" shall mean the work of authorship, whether in Source or Object form,
+    made available under the License, as indicated by a copyright notice that is
+    included in or attached to the work (an example is provided in the Appendix
+    below).
+
+    "Derivative Works" shall mean any work, whether in Source or Object form,
+    that is based on (or derived from) the Work and for which the editorial
+    revisions, annotations, elaborations, or other modifications represent, as a
+    whole, an original work of authorship. For the purposes of this License,
+    Derivative Works shall not include works that remain separable from, or
+    merely link (or bind by name) to the interfaces of, the Work and Derivative
+    Works thereof.
+
+    "Contribution" shall mean any work of authorship, including the original
+    version of the Work and any modifications or additions to that Work or
+    Derivative Works thereof, that is intentionally submitted to Licensor for
+    inclusion in the Work by the copyright owner or by an individual or Legal
+    Entity authorized to submit on behalf of the copyright owner. For the
+    purposes of this definition, "submitted" means any form of electronic,
+    verbal, or written communication sent to the Licensor or its
+    representatives, including but not limited to communication on electronic
+    mailing lists, source code control systems, and issue tracking systems that
+    are managed by, or on behalf of, the Licensor for the purpose of discussing
+    and improving the Work, but excluding communication that is conspicuously
+    marked or otherwise designated in writing by the copyright owner as "Not a
+    Contribution."
+
+    "Contributor" shall mean Licensor and any individual or Legal Entity on
+    behalf of whom a Contribution has been received by Licensor and subsequently
+    incorporated within the Work.
+
+2.  Grant of Copyright License. Subject to the terms and conditions of this
+    License, each Contributor hereby grants to You a perpetual, worldwide,
+    non-exclusive, no-charge, royalty-free, irrevocable copyright license to
+    reproduce, prepare Derivative Works of, publicly display, publicly perform,
+    sublicense, and distribute the Work and such Derivative Works in Source or
+    Object form.
+
+3.  Grant of Patent License. Subject to the terms and conditions of this
+    License, each Contributor hereby grants to You a perpetual, worldwide,
+    non-exclusive, no-charge, royalty-free, irrevocable (except as stated in
+    this section) patent license to make, have made, use, offer to sell, sell,
+    import, and otherwise transfer the Work, where such license applies only to
+    those patent claims licensable by such Contributor that are necessarily
+    infringed by their Contribution(s) alone or by combination of their
+    Contribution(s) with the Work to which such Contribution(s) was submitted.
+    If You institute patent litigation against any entity (including a
+    cross-claim or counterclaim in a lawsuit) alleging that the Work or a
+    Contribution incorporated within the Work constitutes direct or contributory
+    patent infringement, then any patent licenses granted to You under this
+    License for that Work shall terminate as of the date such litigation is
+    filed.
+
+4.  Redistribution. You may reproduce and distribute copies of the Work or
+    Derivative Works thereof in any medium, with or without modifications, and
+    in Source or Object form, provided that You meet the following conditions:
+
+    (a) You must give any other recipients of the Work or Derivative Works a
+    copy of this License; and
+
+    (b) You must cause any modified files to carry prominent notices stating
+    that You changed the files; and
+
+    (c) You must retain, in the Source form of any Derivative Works that You
+    distribute, all copyright, patent, trademark, and attribution notices from
+    the Source form of the Work, excluding those notices that do not pertain to
+    any part of the Derivative Works; and
+
+    (d) If the Work includes a "NOTICE" text file as part of its distribution,
+    then any Derivative Works that You distribute must include a readable copy
+    of the attribution notices contained within such NOTICE file, excluding
+    those notices that do not pertain to any part of the Derivative Works, in at
+    least one of the following places: within a NOTICE text file distributed as
+    part of the Derivative Works; within the Source form or documentation, if
+    provided along with the Derivative Works; or, within a display generated by
+    the Derivative Works, if and wherever such third-party notices normally
+    appear. The contents of the NOTICE file are for informational purposes only
+    and do not modify the License. You may add Your own attribution notices
+    within Derivative Works that You distribute, alongside or as an addendum to
+    the NOTICE text from the Work, provided that such additional attribution
+    notices cannot be construed as modifying the License.
+
+    You may add Your own copyright statement to Your modifications and may
+    provide additional or different license terms and conditions for use,
+    reproduction, or distribution of Your modifications, or for any such
+    Derivative Works as a whole, provided Your use, reproduction, and
+    distribution of the Work otherwise complies with the conditions stated in
+    this License.
+
+5.  Submission of Contributions. Unless You explicitly state otherwise, any
+    Contribution intentionally submitted for inclusion in the Work by You to the
+    Licensor shall be under the terms and conditions of this License, without
+    any additional terms or conditions. Notwithstanding the above, nothing
+    herein shall supersede or modify the terms of any separate license agreement
+    you may have executed with Licensor regarding such Contributions.
+
+6.  Trademarks. This License does not grant permission to use the trade names,
+    trademarks, service marks, or product names of the Licensor, except as
+    required for reasonable and customary use in describing the origin of the
+    Work and reproducing the content of the NOTICE file.
+
+7.  Disclaimer of Warranty. Unless required by applicable law or agreed to in
+    writing, Licensor provides the Work (and each Contributor provides its
+    Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied, including, without limitation, any
+    warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or
+    FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining
+    the appropriateness of using or redistributing the Work and assume any risks
+    associated with Your exercise of permissions under this License.
+
+8.  Limitation of Liability. In no event and under no legal theory, whether in
+    tort (including negligence), contract, or otherwise, unless required by
+    applicable law (such as deliberate and grossly negligent acts) or agreed to
+    in writing, shall any Contributor be liable to You for damages, including
+    any direct, indirect, special, incidental, or consequential damages of any
+    character arising as a result of this License or out of the use or inability
+    to use the Work (including but not limited to damages for loss of goodwill,
+    work stoppage, computer failure or malfunction, or any and all other
+    commercial damages or losses), even if such Contributor has been advised of
+    the possibility of such damages.
+
+9.  Accepting Warranty or Additional Liability. While redistributing the Work or
+    Derivative Works thereof, You may choose to offer, and charge a fee for,
+    acceptance of support, warranty, indemnity, or other liability obligations
+    and/or rights consistent with this License. However, in accepting such
+    obligations, You may act only on Your own behalf and on Your sole
+    responsibility, not on behalf of any other Contributor, and only if You
+    agree to indemnify, defend, and hold each Contributor harmless for any
+    liability incurred by, or claims asserted against, such Contributor by
+    reason of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+Copyright 2025 Pierre Computer Company
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use
+this file except in compliance with the License. You may obtain a copy of the
+License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software distributed
+under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
+CONDITIONS OF ANY KIND, either express or implied. See the License for the
+specific language governing permissions and limitations under the License.

{pierre_storage-0.12.1/pierre_storage.egg-info → pierre_storage-1.0.1}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: pierre-storage
-Version: 0.12.1
+Version: 1.0.1
 Summary: Pierre Git Storage SDK for Python
 Author-email: Pierre <support@pierre.io>
 License-Expression: MIT
 Project-URL: Homepage, https://pierre.io
 Project-URL: Documentation, https://docs.pierre.io
-Project-URL: Repository, https://github.com/pierre/monorepo
-Project-URL: Issues, https://github.com/pierre/monorepo/issues
+Project-URL: Repository, https://github.com/pierrecomputer/pierre
+Project-URL: Issues, https://github.com/pierrecomputer/pierre/issues
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
 Classifier: Programming Language :: Python :: 3
@@ -171,6 +171,16 @@ response = await repo.get_file_stream(
 text = await response.aread()
 print(text.decode())
 
+# Download repository archive (streaming tar.gz)
+archive_response = await repo.get_archive_stream(
+    ref="main",
+    include_globs=["README.md"],
+    exclude_globs=["vendor/**"],
+    archive_prefix="repo/",
+)
+archive_bytes = await archive_response.aread()
+print(len(archive_bytes))
+
 # List all files in the repository
 files = await repo.list_files(
     ref="main",  # optional, defaults to default branch
@@ -244,7 +254,8 @@ print(commit_diff["files"])
 
 ### Creating Commits
 
-The SDK provides a fluent builder API for creating commits with streaming support:
+The SDK provides a fluent builder API for creating commits with streaming
+support:
 
 ```python
 # Create a commit
@@ -268,7 +279,8 @@ print(result["ref_update"]["old_sha"])  # All zeroes when ref is created
 The builder exposes:
 
 - `add_file(path, source, *, mode=None)` - Attach bytes from various sources
-- `add_file_from_string(path, contents, encoding="utf-8", *, mode=None)` - Add text files (defaults to UTF-8)
+- `add_file_from_string(path, contents, encoding="utf-8", *, mode=None)` - Add
+  text files (defaults to UTF-8)
 - `delete_path(path)` - Remove files or folders
 - `send()` - Finalize the commit and receive metadata
 
@@ -289,22 +301,29 @@ The builder exposes:
 }
 ```
 
-If the backend reports a failure, the builder raises a `RefUpdateError` containing the status, reason, and ref details.
+If the backend reports a failure, the builder raises a `RefUpdateError`
+containing the status, reason, and ref details.
 
 **Options:**
 
 - `target_branch` (required): Branch name (without `refs/heads/` prefix)
-- `expected_head_sha` (optional): Branch or commit that must match the remote tip
-- `base_branch` (optional): Name of the branch to use as the base when creating a new branch (without `refs/heads/` prefix)
-- `ephemeral` (optional): Mark the target branch as ephemeral (stored in separate namespace)
-- `ephemeral_base` (optional): Indicates the base branch is ephemeral (requires `base_branch`)
+- `expected_head_sha` (optional): Branch or commit that must match the remote
+  tip
+- `base_branch` (optional): Name of the branch to use as the base when creating
+  a new branch (without `refs/heads/` prefix)
+- `ephemeral` (optional): Mark the target branch as ephemeral (stored in
+  separate namespace)
+- `ephemeral_base` (optional): Indicates the base branch is ephemeral (requires
+  `base_branch`)
 - `commit_message` (required): The commit message
 - `author` (required): Dictionary with `name` and `email`
-- `committer` (optional): Dictionary with `name` and `email` (defaults to author)
+- `committer` (optional): Dictionary with `name` and `email` (defaults to
+  author)
 
 ### Creating Commits from Diff Streams
 
-When you already have a unified diff, you can let the SDK apply it directly without building individual file operations:
+When you already have a unified diff, you can let the SDK apply it directly
+without building individual file operations:
 
 ```python
 diff_text = """\
@@ -327,13 +346,21 @@ result = await repo.create_commit_from_diff(
 print(result["commit_sha"])
 ```
 
-`diff` accepts the same source types as the commit builder (string, bytes, async iterator, etc.). The helper automatically streams the diff to the `/diff-commit` endpoint and returns a `CommitResult`. On conflicts or validation errors, it raises `RefUpdateError` with the server-provided status and message.
+`diff` accepts the same source types as the commit builder (string, bytes, async
+iterator, etc.). The helper automatically streams the diff to the `/diff-commit`
+endpoint and returns a `CommitResult`. On conflicts or validation errors, it
+raises `RefUpdateError` with the server-provided status and message.
 
-You can provide the same metadata options as `create_commit`, including `expected_head_sha`, `base_branch`, `ephemeral`, `ephemeral_base`, and `committer`.
+You can provide the same metadata options as `create_commit`, including
+`expected_head_sha`, `base_branch`, `ephemeral`, `ephemeral_base`, and
+`committer`.
 
-> Files are chunked into 4 MiB segments, allowing streaming of large assets without buffering in memory.
+> Files are chunked into 4 MiB segments, allowing streaming of large assets
+> without buffering in memory.
 
-> The `target_branch` must already exist on the remote repository. To seed an empty repository, omit `expected_head_sha`; the service will create the first commit only when no refs are present.
+> The `target_branch` must already exist on the remote repository. To seed an
+> empty repository, omit `expected_head_sha`; the service will create the first
+> commit only when no refs are present.
 
 **Branching Example:**
 
@@ -353,7 +380,9 @@ result = await (
 
 ### Ephemeral Branches
 
-Ephemeral branches are temporary branches that are stored in a separate namespace. They're useful for preview environments, temporary workspaces, or short-lived feature branches that don't need to be permanent.
+Ephemeral branches are temporary branches that are stored in a separate
+namespace. They're useful for preview environments, temporary workspaces, or
+short-lived feature branches that don't need to be permanent.
 
 **Creating an ephemeral branch:**
 
@@ -424,9 +453,12 @@ print(result["target_branch"])  # "feature/awesome-change"
 
 - Ephemeral branches are stored separately from regular branches
 - Use `ephemeral=True` when creating commits, reading files, or listing files
-- Use `ephemeral_base=True` when branching off another ephemeral branch (requires `base_branch`)
-- Promote an ephemeral branch with `repo.promote_ephemeral_branch()`; omit `target_branch` to keep the same name
-- Ephemeral branches are ideal for temporary previews, CI/CD environments, or experiments
+- Use `ephemeral_base=True` when branching off another ephemeral branch
+  (requires `base_branch`)
+- Promote an ephemeral branch with `repo.promote_ephemeral_branch()`; omit
+  `target_branch` to keep the same name
+- Ephemeral branches are ideal for temporary previews, CI/CD environments, or
+  experiments
 
 ### Streaming Large Files
 
@@ -476,9 +508,11 @@ commits = await repo.list_commits()
 
 **How it works:**
 
-1. When you create a repo with `base_repo`, Pierre links it to the specified GitHub repository
+1. When you create a repo with `base_repo`, Pierre links it to the specified
+   GitHub repository
 2. The `pull_upstream()` method fetches the latest changes from GitHub
-3. You can then use all Pierre SDK features (diffs, commits, file access) on the synced content
+3. You can then use all Pierre SDK features (diffs, commits, file access) on the
+   synced content
 4. The provider is automatically set to `"github"` when using `base_repo`
 
 ### Forking Repositories
@@ -564,6 +598,16 @@ class Repo:
         ttl: Optional[int] = None,
     ) -> Response: ...
 
+    async def get_archive_stream(
+        self,
+        *,
+        ref: Optional[str] = None,
+        include_globs: Optional[List[str]] = None,
+        exclude_globs: Optional[List[str]] = None,
+        archive_prefix: Optional[str] = None,
+        ttl: Optional[int] = None,
+    ) -> Response: ...
+
     async def list_files(
         self,
         *,
@@ -724,17 +768,20 @@ else:
 
 ## Authentication
 
-The SDK uses JWT (JSON Web Tokens) for authentication. When you call `get_remote_url()`, it:
+The SDK uses JWT (JSON Web Tokens) for authentication. When you call
+`get_remote_url()`, it:
 
 1. Creates a JWT with your name, repository ID, and requested permissions
 2. Signs it with your private key (ES256, RS256, or EdDSA)
 3. Embeds it in the Git remote URL as the password
 
-The generated URLs are compatible with standard Git clients and include all necessary authentication.
+The generated URLs are compatible with standard Git clients and include all
+necessary authentication.
 
 ### Manual JWT Generation
 
-For advanced use cases, you can generate JWTs manually using the `generate_jwt` helper:
+For advanced use cases, you can generate JWTs manually using the `generate_jwt`
+helper:
 
 ```python
 from pierre_storage import generate_jwt
@@ -761,11 +808,13 @@ git_url = f"https://t:{token}@your-name.code.storage/your-repo-id.git"
 - `key_pem` (required): Private key in PEM format (PKCS8)
 - `issuer` (required): Token issuer (your customer name)
 - `repo_id` (required): Repository identifier
-- `scopes` (optional): List of permission scopes. Defaults to `["git:write", "git:read"]`
+- `scopes` (optional): List of permission scopes. Defaults to
+  `["git:write", "git:read"]`
   - Available scopes: `"git:read"`, `"git:write"`, `"repo:write"`
 - `ttl` (optional): Time-to-live in seconds. Defaults to 31536000 (1 year)
 
-The function automatically detects the key type (RSA, EC, or EdDSA) and uses the appropriate signing algorithm (RS256, ES256, or EdDSA).
+The function automatically detects the key type (RSA, EC, or EdDSA) and uses the
+appropriate signing algorithm (RS256, ES256, or EdDSA).
 
 ## Error Handling
 

{pierre_storage-0.12.1 → pierre_storage-1.0.1}/README.md

@@ -135,6 +135,16 @@ response = await repo.get_file_stream(
 text = await response.aread()
 print(text.decode())
 
+# Download repository archive (streaming tar.gz)
+archive_response = await repo.get_archive_stream(
+    ref="main",
+    include_globs=["README.md"],
+    exclude_globs=["vendor/**"],
+    archive_prefix="repo/",
+)
+archive_bytes = await archive_response.aread()
+print(len(archive_bytes))
+
 # List all files in the repository
 files = await repo.list_files(
     ref="main",  # optional, defaults to default branch
@@ -208,7 +218,8 @@ print(commit_diff["files"])
 
 ### Creating Commits
 
-The SDK provides a fluent builder API for creating commits with streaming support:
+The SDK provides a fluent builder API for creating commits with streaming
+support:
 
 ```python
 # Create a commit
@@ -232,7 +243,8 @@ print(result["ref_update"]["old_sha"])  # All zeroes when ref is created
 The builder exposes:
 
 - `add_file(path, source, *, mode=None)` - Attach bytes from various sources
-- `add_file_from_string(path, contents, encoding="utf-8", *, mode=None)` - Add text files (defaults to UTF-8)
+- `add_file_from_string(path, contents, encoding="utf-8", *, mode=None)` - Add
+  text files (defaults to UTF-8)
 - `delete_path(path)` - Remove files or folders
 - `send()` - Finalize the commit and receive metadata
 
@@ -253,22 +265,29 @@ The builder exposes:
 }
 ```
 
-If the backend reports a failure, the builder raises a `RefUpdateError` containing the status, reason, and ref details.
+If the backend reports a failure, the builder raises a `RefUpdateError`
+containing the status, reason, and ref details.
 
 **Options:**
 
 - `target_branch` (required): Branch name (without `refs/heads/` prefix)
-- `expected_head_sha` (optional): Branch or commit that must match the remote tip
-- `base_branch` (optional): Name of the branch to use as the base when creating a new branch (without `refs/heads/` prefix)
-- `ephemeral` (optional): Mark the target branch as ephemeral (stored in separate namespace)
-- `ephemeral_base` (optional): Indicates the base branch is ephemeral (requires `base_branch`)
+- `expected_head_sha` (optional): Branch or commit that must match the remote
+  tip
+- `base_branch` (optional): Name of the branch to use as the base when creating
+  a new branch (without `refs/heads/` prefix)
+- `ephemeral` (optional): Mark the target branch as ephemeral (stored in
+  separate namespace)
+- `ephemeral_base` (optional): Indicates the base branch is ephemeral (requires
+  `base_branch`)
 - `commit_message` (required): The commit message
 - `author` (required): Dictionary with `name` and `email`
-- `committer` (optional): Dictionary with `name` and `email` (defaults to author)
+- `committer` (optional): Dictionary with `name` and `email` (defaults to
+  author)
 
 ### Creating Commits from Diff Streams
 
-When you already have a unified diff, you can let the SDK apply it directly without building individual file operations:
+When you already have a unified diff, you can let the SDK apply it directly
+without building individual file operations:
 
 ```python
 diff_text = """\
@@ -291,13 +310,21 @@ result = await repo.create_commit_from_diff(
 print(result["commit_sha"])
 ```
 
-`diff` accepts the same source types as the commit builder (string, bytes, async iterator, etc.). The helper automatically streams the diff to the `/diff-commit` endpoint and returns a `CommitResult`. On conflicts or validation errors, it raises `RefUpdateError` with the server-provided status and message.
+`diff` accepts the same source types as the commit builder (string, bytes, async
+iterator, etc.). The helper automatically streams the diff to the `/diff-commit`
+endpoint and returns a `CommitResult`. On conflicts or validation errors, it
+raises `RefUpdateError` with the server-provided status and message.
 
-You can provide the same metadata options as `create_commit`, including `expected_head_sha`, `base_branch`, `ephemeral`, `ephemeral_base`, and `committer`.
+You can provide the same metadata options as `create_commit`, including
+`expected_head_sha`, `base_branch`, `ephemeral`, `ephemeral_base`, and
+`committer`.
 
-> Files are chunked into 4 MiB segments, allowing streaming of large assets without buffering in memory.
+> Files are chunked into 4 MiB segments, allowing streaming of large assets
+> without buffering in memory.
 
-> The `target_branch` must already exist on the remote repository. To seed an empty repository, omit `expected_head_sha`; the service will create the first commit only when no refs are present.
+> The `target_branch` must already exist on the remote repository. To seed an
+> empty repository, omit `expected_head_sha`; the service will create the first
+> commit only when no refs are present.
 
 **Branching Example:**
 
@@ -317,7 +344,9 @@ result = await (
 
 ### Ephemeral Branches
 
-Ephemeral branches are temporary branches that are stored in a separate namespace. They're useful for preview environments, temporary workspaces, or short-lived feature branches that don't need to be permanent.
+Ephemeral branches are temporary branches that are stored in a separate
+namespace. They're useful for preview environments, temporary workspaces, or
+short-lived feature branches that don't need to be permanent.
 
 **Creating an ephemeral branch:**
 
@@ -388,9 +417,12 @@ print(result["target_branch"])  # "feature/awesome-change"
 
 - Ephemeral branches are stored separately from regular branches
 - Use `ephemeral=True` when creating commits, reading files, or listing files
-- Use `ephemeral_base=True` when branching off another ephemeral branch (requires `base_branch`)
-- Promote an ephemeral branch with `repo.promote_ephemeral_branch()`; omit `target_branch` to keep the same name
-- Ephemeral branches are ideal for temporary previews, CI/CD environments, or experiments
+- Use `ephemeral_base=True` when branching off another ephemeral branch
+  (requires `base_branch`)
+- Promote an ephemeral branch with `repo.promote_ephemeral_branch()`; omit
+  `target_branch` to keep the same name
+- Ephemeral branches are ideal for temporary previews, CI/CD environments, or
+  experiments
 
 ### Streaming Large Files
 
@@ -440,9 +472,11 @@ commits = await repo.list_commits()
 
 **How it works:**
 
-1. When you create a repo with `base_repo`, Pierre links it to the specified GitHub repository
+1. When you create a repo with `base_repo`, Pierre links it to the specified
+   GitHub repository
 2. The `pull_upstream()` method fetches the latest changes from GitHub
-3. You can then use all Pierre SDK features (diffs, commits, file access) on the synced content
+3. You can then use all Pierre SDK features (diffs, commits, file access) on the
+   synced content
 4. The provider is automatically set to `"github"` when using `base_repo`
 
 ### Forking Repositories
@@ -528,6 +562,16 @@ class Repo:
         ttl: Optional[int] = None,
     ) -> Response: ...
 
+    async def get_archive_stream(
+        self,
+        *,
+        ref: Optional[str] = None,
+        include_globs: Optional[List[str]] = None,
+        exclude_globs: Optional[List[str]] = None,
+        archive_prefix: Optional[str] = None,
+        ttl: Optional[int] = None,
+    ) -> Response: ...
+
     async def list_files(
         self,
         *,
@@ -688,17 +732,20 @@ else:
 
 ## Authentication
 
-The SDK uses JWT (JSON Web Tokens) for authentication. When you call `get_remote_url()`, it:
+The SDK uses JWT (JSON Web Tokens) for authentication. When you call
+`get_remote_url()`, it:
 
 1. Creates a JWT with your name, repository ID, and requested permissions
 2. Signs it with your private key (ES256, RS256, or EdDSA)
 3. Embeds it in the Git remote URL as the password
 
-The generated URLs are compatible with standard Git clients and include all necessary authentication.
+The generated URLs are compatible with standard Git clients and include all
+necessary authentication.
 
 ### Manual JWT Generation
 
-For advanced use cases, you can generate JWTs manually using the `generate_jwt` helper:
+For advanced use cases, you can generate JWTs manually using the `generate_jwt`
+helper:
 
 ```python
 from pierre_storage import generate_jwt
@@ -725,11 +772,13 @@ git_url = f"https://t:{token}@your-name.code.storage/your-repo-id.git"
 - `key_pem` (required): Private key in PEM format (PKCS8)
 - `issuer` (required): Token issuer (your customer name)
 - `repo_id` (required): Repository identifier
-- `scopes` (optional): List of permission scopes. Defaults to `["git:write", "git:read"]`
+- `scopes` (optional): List of permission scopes. Defaults to
+  `["git:write", "git:read"]`
   - Available scopes: `"git:read"`, `"git:write"`, `"repo:write"`
 - `ttl` (optional): Time-to-live in seconds. Defaults to 31536000 (1 year)
 
-The function automatically detects the key type (RSA, EC, or EdDSA) and uses the appropriate signing algorithm (RS256, ES256, or EdDSA).
+The function automatically detects the key type (RSA, EC, or EdDSA) and uses the
+appropriate signing algorithm (RS256, ES256, or EdDSA).
 
 ## Error Handling
 

{pierre_storage-0.12.1 → pierre_storage-1.0.1}/pierre_storage/client.py

@@ -1,6 +1,7 @@
 """Main client for Pierre Git Storage SDK."""
 
 import uuid
+from datetime import datetime, timezone
 from typing import Any, Dict, Optional, cast
 from urllib.parse import urlencode
 
@@ -216,6 +217,7 @@ class GitStorage:
             name,
             api_version,
             self._generate_jwt,
+            created_at=datetime.now(timezone.utc).isoformat(),
         )
 
     async def list_repos(
@@ -317,6 +319,7 @@ class GitStorage:
 
             body = response.json()
             default_branch = body.get("default_branch", "main")
+            created_at = body.get("created_at", "")
 
         # These are guaranteed to be set in __init__
         api_base_url: str = self.options["api_base_url"]  # type: ignore[assignment]
@@ -332,6 +335,7 @@ class GitStorage:
             name,
             api_version,
             self._generate_jwt,
+            created_at=created_at,
         )
 
     async def delete_repo(