python-gitea 0.10.0__tar.gz → 0.11.0__tar.gz

{python_gitea-0.10.0 → python_gitea-0.11.0}/.github/workflows/support_floor_update.yml

@@ -22,7 +22,7 @@ jobs:
 
             - name: Apply support policy (spec0, from pyproject tool table)
               id: policy
-              uses: isaac-cf-wong/dependency-support-policy-action@7cce60e19b902747b4267c4f8e53820e3f3656ea # v0.2.4
+              uses: isaac-cf-wong/dependency-support-policy-action@c00466ca1b1d902260e56e087c072cbb41ac038b # v0.2.5
               with:
                   mode: update
 

{python_gitea-0.10.0 → python_gitea-0.11.0}/.pre-commit-config.yaml

@@ -16,7 +16,7 @@ repos:
           - id: check-json
 
     - repo: https://github.com/astral-sh/ruff-pre-commit
-      rev: v0.16.3
+      rev: v0.16.4
       hooks:
           - id: ruff
             args: [--fix, --config=pyproject.toml]

{python_gitea-0.10.0 → python_gitea-0.11.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: python-gitea
-Version: 0.10.0
+Version: 0.11.0
 Summary: A Python package for interacting with the Gitea API, offering a simple interface to access repositories, users, organizations, issues, and more for automation and data management.
 Project-URL: Documentation, https://isaac-cf-wong.github.io/python-gitea
 Project-URL: Source, https://github.com/isaac-cf-wong/python-gitea
@@ -36,6 +36,7 @@ Description-Content-Type: text/markdown
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/isaac-cf-wong/python-gitea/blob/main/LICENSE)
 [![Security: bandit](https://img.shields.io/badge/security-bandit-yellow.svg)](https://github.com/PyCQA/bandit)
 [![DOI](https://zenodo.org/badge/1129170965.svg)](https://doi.org/10.5281/zenodo.18211496)
+[![SPEC 0 — Minimum Supported Dependencies](https://img.shields.io/badge/SPEC-0-green?labelColor=%23004811&color=%235CA038)](https://scientific-python.org/specs/spec-0000/)
 
 A Python package for interacting with the Gitea API. It provides a simple,
 intuitive interface to access Gitea repositories, users, organizations, issues,
@@ -45,7 +46,8 @@ data retrieval, and management tasks.
 ## Features
 
 - **Full API Coverage**: Repositories, users, organizations, issues, pull
-  requests, comments, labels, milestones, notifications, and projects.
+  requests, comments, labels, milestones, notifications, projects, and Actions
+  workflows, runs, and job logs.
 - **Easy Authentication**: Token-based authentication, with multiple saved
   accounts and a default-account fallback.
 - **Asynchronous Support**: Built with `async`/`await` for non-blocking

{python_gitea-0.10.0 → python_gitea-0.11.0}/README.md

@@ -9,6 +9,7 @@
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/isaac-cf-wong/python-gitea/blob/main/LICENSE)
 [![Security: bandit](https://img.shields.io/badge/security-bandit-yellow.svg)](https://github.com/PyCQA/bandit)
 [![DOI](https://zenodo.org/badge/1129170965.svg)](https://doi.org/10.5281/zenodo.18211496)
+[![SPEC 0 — Minimum Supported Dependencies](https://img.shields.io/badge/SPEC-0-green?labelColor=%23004811&color=%235CA038)](https://scientific-python.org/specs/spec-0000/)
 
 A Python package for interacting with the Gitea API. It provides a simple,
 intuitive interface to access Gitea repositories, users, organizations, issues,
@@ -18,7 +19,8 @@ data retrieval, and management tasks.
 ## Features
 
 - **Full API Coverage**: Repositories, users, organizations, issues, pull
-  requests, comments, labels, milestones, notifications, and projects.
+  requests, comments, labels, milestones, notifications, projects, and Actions
+  workflows, runs, and job logs.
 - **Easy Authentication**: Token-based authentication, with multiple saved
   accounts and a default-account fallback.
 - **Asynchronous Support**: Built with `async`/`await` for non-blocking

{python_gitea-0.10.0 → python_gitea-0.11.0}/docs/dev/architecture.md

@@ -35,6 +35,15 @@ src/gitea/
 │   └── manager.py           # ConfigManager (load/save/CRUD accounts)
 ├── resource/                # Resource base class
 │   └── resource.py          # Shared request helpers for resources
+├── actions/                 # Actions resource (sync + async), composed per family
+│   ├── base.py              # Every Actions path and query parameter
+│   ├── scope.py             # Which scope a set of coordinates addresses
+│   ├── actions.py           # Workflows, runs, jobs; composes the families below
+│   ├── run_management.py    # Cancel, approve, rerun, delete a run
+│   ├── artifact.py          # The files a run produced, archive included
+│   ├── secret.py            # Write-only secrets of a scope
+│   ├── variable.py          # Their readable counterpart
+│   └── runner.py            # Runners of a scope, and the registration token
 ├── issue/                   # Issue resource (sync + async)
 ├── pull_request/            # Pull request resource (sync + async)
 ├── repository/              # Repository resource (sync + async)
@@ -48,6 +57,7 @@ src/gitea/
 ├── cli/                     # Typer CLI application
 │   ├── main.py              # gitea-cli entry point, command registration
 │   ├── config/              # config commands
+│   ├── actions/             # actions workflow, run, job, artifact, secret, variable, runner commands
 │   ├── issue/               # issue + issue dependency commands
 │   ├── pull_request/        # pull-request commands
 │   ├── comment/             # comment commands
@@ -80,6 +90,7 @@ Each client exposes one attribute per resource:
 
 ```python
 with Gitea(token="...", base_url="...") as client:
+    client.actions        # Actions
     client.issue          # Issue
     client.pull_request   # PullRequest
     client.repository     # Repository
@@ -107,6 +118,34 @@ it, so the resource methods stay one-to-one with the API. For example,
 `gitea.issue.project_column` resolves the board column an issue's card sits in,
 which Gitea only reveals through the project's column listings.
 
+`actions` is the one resource split further, into a module per family - runs,
+artifacts, secrets, variables, runners - which `Actions` and `AsyncActions`
+compose. Gitea's Actions API is large enough that one class per client would be
+a file nobody reads end to end, and the families differ from each other in ways
+worth writing down beside their own methods: which listings answer with an
+object and which with a bare array, which endpoints answer with a file rather
+than a document, and which scopes each family exists at. The path building for
+all of them stays in one `base.py`, so every URL the resource can address is in
+one place.
+
+That package's `__init__.py` re-exports nothing, unlike its neighbours'. With
+thirteen modules an eager re-export would make `import gitea.actions.scope`
+execute all of them, and would put each in an import cycle: importing a
+submodule imports its package, so a package that imports its submodules is one
+they import back. `tests/actions/test_actions_imports.py` pins both properties.
+
+The neighbours keep their re-exports and avoid the same two costs by resolving
+them on first read instead, through a module-level `__getattr__` (PEP 562) that
+`gitea._lazy.lazy_reexports` builds from a table of name against origin module.
+`from gitea.issue import Issue` works exactly as it did, while
+`import gitea.issue.base` no longer executes either client - and the package no
+longer imports the submodules that import it back, which is where 44 of the
+import cycles in this tree came from. Each such package keeps a `TYPE_CHECKING`
+block naming the same imports, so editors and type checkers still resolve the
+names statically; that block does not execute, so it reintroduces no cycle.
+`tests/test_lazy_reexports.py` pins the public names, the laziness, and the
+absence of any module-level import cycle anywhere in `gitea`.
+
 ## CLI Layer
 
 The CLI is a single Typer application registered in `cli/main.py`. Each resource