kaggle 2.2.4__tar.gz → 2.2.5__tar.gz

{kaggle-2.2.4 → kaggle-2.2.5}/CHANGELOG.md

@@ -3,6 +3,46 @@ Changelog
 
 ### Next
 
+### 2.2.5
+
+* Require `certifi >= 2026.10.19`, which drops the compromised emSign/eMudhra root CAs ([GHSA-6q48-6c7w-9gw2](https://github.com/certifi/python-certifi/security/advisories/GHSA-6q48-6c7w-9gw2)). `kaggle` only pulled in certifi through `requests`, which sets no minimum, so an existing install could keep a certifi that would accept a forged kaggle.com certificate and leak the user's API token to a man-in-the-middle
+* Reject kernel version numbers in `kaggle kernels delete` instead of failing with a `ValueError` when a version is included in `<owner>/<kernel>/<version>`
+* Report a 404 from `kaggle competitions submit` with a competition-specific hint on stderr, naming the notebook and version for code submissions. The check never matched a 404, so users got the generic `<owner>/<slug>` hint instead
+* Exit non-zero from `kaggle competitions submit` when the submission file upload fails. It printed "Could not submit to competition" and exited 0, so scripts treated the failed submission as a success
+* Include the UTC offset (`+00:00`) in `refreshAt` timestamps displayed by `kaggle quota`
+* Recommend installing with `pipx` or `uv` and add troubleshooting guidance for `externally-managed-environment` errors in the installation docs
+* Stream `kaggle kernels output` files to disk through the same download path as datasets and competitions, with a read timeout, a size check, and resume after a dropped connection. Each file used to be read into memory whole, so a 512 MiB output took about 1.2 GB of RAM, and a dropped connection failed the command and left an empty file behind
+* Honor the version in `<owner>/<kernel>/<version>` for `kaggle kernels pull`, `output`, `status`, `files` and `logs`, which previously returned 403 for `pull` and acted on the latest version for the others
+* Clarify in `--accelerator` help and kernels docs that `NvidiaTeslaT4` maps to GPU T4 x2 and `TpuV5E8` maps to TPU v5e-8
+* Reject dataset version numbers in `kaggle datasets delete` to prevent unintentionally deleting an entire dataset when targeting a single version
+* Show why a submission failed in `kaggle competitions submission <ref>`, which already comes back in the API response but was not displayed
+* Honor `-k/--kernel` in `kaggle kernels pull`, which was ignored when the positional kernel argument was omitted, causing the CLI to fall back to the local `kernel-metadata.json` and pull a different kernel
+* Refuse to write a `kaggle kernels output` file whose server-supplied name resolves outside the requested `--path` directory
+* Add `--no-run` to `kaggle kernels push` to save a new version without executing the notebook, the equivalent of Quick Save in the web UI
+* Honor `--unzip` when downloading a single file with `kaggle datasets download -f`, which extracts the file from the zip archive the server wraps large files in, and add `--unzip` to `kaggle competitions download`
+* Fix misleading validation error messages in `kaggle competitions submit` when `--kernel`, `--version`, or `--file` is missing for a code competition submission
+* Keep the requested folder when downloading a single file with `kaggle datasets download -f` or `kaggle competitions download -f`, instead of writing it to the download root
+* Report `slug` instead of `title` in the `kaggle datasets create` error message when the requested slug is already in use
+* Prevent HTTP errors during resumed `Range` downloads from overwriting existing partial download files
+* Check the HTTP status when downloading `kaggle kernels output` files so error responses are not saved as output files
+* Add `kaggle competitions host-add <comp> -u <user>` to grant host access on a competition to a Kaggle user
+* Suggest a next step on 403/404/429/5xx API errors, report unexpected errors as bugs instead of a traceback (with a new `--debug` flag), and list common examples in `kaggle --help`
+* Guard tar extraction in `kaggle models instances versions download --untar` against path traversal
+* Store resumable upload state in a private per-user directory (`0700`) and verify directory ownership and permissions before use
+* Add `kaggle benchmarks quota` to show Model Proxy (AI inference) spend quota, and bump `kagglesdk` to `>= 0.1.38`
+* Honor `--untar` in `kaggle models instances versions download` when the archive is already cached locally
+* Write kernel log files using UTF-8 in `kaggle kernels output` to avoid `UnicodeEncodeError` on Windows
+* Exclude omitted `overview` and `usage` fields from the update mask when updating a model instance
+* Add `kaggle competitions submission-download <id>` to download the submitted file for a single submission (requires `kagglesdk >= 0.1.36`)
+* Add `deadline` (Competition Deadline) to the competition settings command and bump `kagglesdk` to `>= 0.1.36`
+* Warn when `kaggle kernels push` requests a retired accelerator (`NvidiaTeslaP100`, `TpuV38`, `Tpu1VmV38`, `TpuV232` or `TpuV2256`), since the server runs the session on a replacement instead. Drop the retired shapes from the docs
+* Abort dataset, model version, and competition data uploads when a file upload fails instead of skipping the failed file and creating a partial upload
+* Use GitHub alerts and fix the `LLMS_AVAILABLE` token reference in the benchmarks documentation
+* Add unified `kaggle search` command across competitions, datasets, notebooks, models, users, and discussions
+* Parse duration suffixes (`s`, `m`, `h`, `d`, `w`) in `kaggle auth print-access-token --expiration` instead of raising a `TypeError`
+* Add `--wait`/`--poll-interval` to `kaggle competitions submit` to wait for scoring, and add `kaggle competitions submission <ref>` to look up a single submission's status and score
+* Show `N/A` instead of `Fail` in `kaggle benchmarks leaderboard` for a task result the server returned without a pass/fail or numeric score, which was reported as a failed task
+
 ### 2.2.4
 
 * fix(benchmarks): support owner/task separator in benchmark commands (#1146)

{kaggle-2.2.4 → kaggle-2.2.5}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: kaggle
-Version: 2.2.4
+Version: 2.2.5
 Summary: Access Kaggle resources anywhere
 Project-URL: Homepage, https://github.com/Kaggle/kaggle-cli
 Project-URL: Issues, https://github.com/Kaggle/kaggle-cli/issues
@@ -213,8 +213,9 @@ Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3
 Requires-Python: >=3.11
 Requires-Dist: bleach
+Requires-Dist: certifi>=2026.10.19
 Requires-Dist: jupytext
-Requires-Dist: kagglesdk<1.0,>=0.1.35
+Requires-Dist: kagglesdk<1.0,>=0.1.38
 Requires-Dist: packaging
 Requires-Dist: protobuf
 Requires-Dist: python-dateutil

{kaggle-2.2.4 → kaggle-2.2.5}/docs/README.md

@@ -4,15 +4,42 @@ Welcome to the Kaggle CLI documentation. This guide provides detailed informatio
 
 ## Installation
 
-Note: Ensure you have Python 3.11+ and the package manager `pip` installed.
+Note: Ensure you have Python 3.11+.
 
-Install the `kaggle` package with [pip](https://pypi.org/project/pip/):
+Recommended: install with [pipx](https://pipx.pypa.io/) or [uv](https://docs.astral.sh/uv/),
+which installs the CLI in an isolated environment and works on all platforms:
+
+```sh
+pipx install kaggle
+# or
+uv tool install kaggle
+```
+
+### Alternative: pip
+
+You can also install the package with [pip](https://pypi.org/project/pip/):
 
 ```sh
 pip install kaggle
 ```
 
-If you run into a `Command kaggle not found` error, ensure that your Python executable scripts are in your $PATH. For a local user install on Linux, the default location is `~/.local/bin`. On Windows, the default location is `$PYTHON_HOME/Scripts`.
+### Troubleshooting
+
+If you see `error: externally-managed-environment`, your operating system protects its
+system Python (this is the default on recent Debian and Ubuntu releases, among others).
+Use pipx or uv as described above. If that is not an option, you can override the
+protection with `--break-system-packages`:
+
+```sh
+pip install --break-system-packages kaggle
+```
+
+Note: this installs the package into the system Python and may conflict with packages
+managed by your OS.
+
+If you run into a `Command kaggle not found` error, ensure that your Python executable
+scripts are in your $PATH. For a local user install on Linux, the default location is
+`~/.local/bin`. On Windows, the default location is `$PYTHON_HOME/Scripts`.
 
 ## Authentication
 

{kaggle-2.2.4 → kaggle-2.2.5}/docs/benchmarks.md

@@ -6,6 +6,7 @@ The top-level command is `kaggle benchmarks` (alias: `kaggle b`), which has the
 
 *   **`auth`** — Fetch Model Proxy credentials.
 *   **`init`** — Fetch credentials and default environment variables for local development.
+*   **`quota`** — Show your Model Proxy (AI inference) spend quota.
 *   **`leaderboard`** — Get benchmark leaderboard information.
 *   **`tasks`** (alias: `t`) — Manage benchmark tasks (push, run, list, status, download, log, models, delete, publish).
 *   **`topics`** — Browse discussion topics for a benchmark.
@@ -79,7 +80,8 @@ In addition to the three credential variables written by `auth`, `init` also wri
 *   `LLM_DEFAULT_EVAL` — Default model slug for evaluation.
 *   `LLMS_AVAILABLE` — Comma-separated list of available model slugs.
 
-> **Note:** `LLMS_AVAILABLE` is a curated subset of models intended for local development and testing — it is **not** the full set of available models, and the Model Proxy token itself is not restricted to these models. To see all available models, use `kaggle benchmarks tasks models`. To run a task against any model (including those not in `LLMS_AVAILABLE`), use `kaggle benchmarks tasks run`, which executes on Kaggle's infrastructure with access to the full model catalog.
+> [!WARNING]
+> `LLMS_AVAILABLE` is a curated subset of models intended for local development and testing — it is **not** the full set of available models, and the Model Proxy token minted for local development **is** restricted to these models. To see all available models, use `kaggle benchmarks tasks models`. To run a task against any model (including those not in `LLMS_AVAILABLE`), use `kaggle benchmarks tasks run`, which executes on Kaggle's infrastructure with access to the full model catalog.
 
 `init` also creates two files alongside the example file:
 
@@ -90,6 +92,37 @@ If either file already exists, it is skipped without overwriting.
 
 ---
 
+## `kaggle benchmarks quota`
+
+Shows your current Model Proxy (AI inference) spend quota, one row per refill period.
+
+**Usage:**
+
+```bash
+kaggle benchmarks quota [options]
+```
+
+**Options:**
+
+*   `-v, --csv`: Print results in CSV format.
+*   `--format <FORMAT>`: Print results in the selected format (`csv`, `table`, `json`).
+
+**Example:**
+
+```bash
+$ kaggle b quota
+period   used    remaining  total    refillAt
+-------  ------  ---------  -------  -------------------------
+Daily    $1.20   $3.80      $5.00    2026-08-08T00:00:00+00:00
+Monthly  $14.50  $85.50     $100.00  2026-09-01T00:00:00+00:00
+```
+
+**Purpose:**
+
+Amounts are in USD and reflect inference spend through the Model Proxy — this is separate from the top-level `kaggle quota` command, which reports weekly GPU and TPU accelerator *hours*. `remaining` is derived as `total - used` and is clamped at `$0.00`, so an overage shows as zero remaining rather than a negative balance.
+
+---
+
 ## `kaggle benchmarks leaderboard`
 
 Get benchmark leaderboard information.
@@ -217,7 +250,8 @@ kaggle benchmarks tasks push <TASK> -f <FILE> [options]
 
 This command reads a `.py` file, converts it to a Jupyter notebook format, and uploads it to Kaggle as a benchmark task. If a task with the same slug already exists, a new version is created. The file is validated to ensure it contains a `@task` decorator matching the given task name.
  
-**Note on dataset attachment:** When `--kaggle-dataset` / `-d` is specified, the listed datasets are attached to the task's underlying notebook kernel. During execution, they are accessible at `/kaggle/input/<dataset-slug>/` by default, falling back to `/kaggle/input/<owner>/<dataset-slug>/` in the event of a naming conflict. If you re-push without `-d`, all previously-attached datasets are detached (a warning is printed). To preserve datasets across pushes, re-specify them each time. If any specified dataset is invalid, non-existent, or inaccessible, the push command will **fail** with an error: `Failed to push task: Failed to attach the following data sources (not found or inaccessible): <dataset>`.
+> [!NOTE]
+> **On dataset attachment:** When `--kaggle-dataset` / `-d` is specified, the listed datasets are attached to the task's underlying notebook kernel. During execution, they are accessible at `/kaggle/input/<dataset-slug>/` by default, falling back to `/kaggle/input/<owner>/<dataset-slug>/` in the event of a naming conflict. If you re-push without `-d`, all previously-attached datasets are detached (a warning is printed). To preserve datasets across pushes, re-specify them each time. If any specified dataset is invalid, non-existent, or inaccessible, the push command will **fail** with an error: `Failed to push task: Failed to attach the following data sources (not found or inaccessible): <dataset>`.
 
 ---
 

{kaggle-2.2.4 → kaggle-2.2.5}/docs/competition_creation.md

@@ -7,6 +7,7 @@ public competition-creation API endpoints (kagglesdk 0.1.31+):
 - [`kaggle competitions create`](#kaggle-competitions-create)
 - [`kaggle competitions pages create`](#kaggle-competitions-pages-create)
 - [`kaggle competitions hosts`](#kaggle-competitions-hosts)
+- [`kaggle competitions host-add`](#kaggle-competitions-host-add)
 - [`kaggle competitions settings get`](#kaggle-competitions-settings-get)
 - [`kaggle competitions settings update`](#kaggle-competitions-settings-update)
 - [`kaggle competitions data update`](#kaggle-competitions-data-update)
@@ -358,6 +359,47 @@ Output columns: `userName`, `displayName`, `id`, `profileUrl`.
 
 ---
 
+## `kaggle competitions host-add`
+
+Grants host access on a competition you host to another Kaggle user. Hosts can
+edit settings, upload data, and launch the competition, so you are asked to
+confirm before the change is made.
+
+**Usage:**
+
+```bash
+kaggle competitions host-add <competition> -u <user> [-y]
+```
+
+**Arguments:**
+
+- `<competition>`: The competition slug.
+
+**Options:**
+
+- `-u, --user <USER>`: Kaggle user name (URL slug, e.g. `kerneler`) of the user
+  to add as a host. Required.
+- `-y, --yes`: Skip the confirmation prompt.
+- `-q, --quiet`: Suppress the "Using competition" message.
+
+**Examples:**
+
+```bash
+# Prompts for confirmation before granting access.
+kaggle competitions host-add my-comp -u alice
+
+# Skip the prompt (for scripts).
+kaggle competitions host-add my-comp -u alice -y
+```
+
+Verify the result with `kaggle competitions hosts my-comp`.
+
+> **Note:** This command is named `host-add` rather than `hosts add` because
+> `hosts` takes the competition as a positional argument, and argparse cannot
+> distinguish a competition slug from a subcommand name.
+
+---
+
 ## `kaggle competitions settings get`
 
 Shows the unified settings blob for a competition you host — the same set of
@@ -437,13 +479,25 @@ Toggle a single boolean:
 kaggle competitions settings update my-comp -f ./disable-leaderboard.json
 ```
 
-Bump the code-competition runtime caps and set the team-merger deadline
-(YAML, mixing types):
+Set the competition deadline:
+
+```json
+// deadline.json
+{ "deadline": "2027-02-01T23:59:00Z" }
+```
+
+```bash
+kaggle competitions settings update my-comp -f ./deadline.json
+```
+
+Bump the code-competition runtime caps and set the competition and team-merger
+deadlines (YAML, mixing types):
 
 ```yaml
 # tune.yaml
 max_cpu_runtime_minutes: 540
 max_gpu_runtime_minutes: 720
+deadline: 2027-02-01T23:59:00Z
 team_merger_explicit_deadline: 2027-01-15T00:00:00Z
 rules_required: true
 ```

{kaggle-2.2.4 → kaggle-2.2.5}/docs/competitions.md

@@ -99,9 +99,10 @@ kaggle competitions download <COMPETITION> [options]
 
 **Options:**
 
-*   `-f, --file <FILE_NAME>`: Specific file to download (downloads all if not specified).
+*   `-f, --file <FILE_NAME>`: Specific file to download (downloads all if not specified). A file inside a folder, such as `train/labels.csv`, keeps that folder under the download path.
 *   `-p, --path <PATH>`: Folder to download files to (defaults to current directory).
 *   `-w, --wp`: Download files to the current working path (equivalent to `-p .`).
+*   `--unzip`: Unzip the downloaded file (deletes the .zip file afterwards).
 *   `-o, --force`: Force download, overwriting existing files.
 *   `-q, --quiet`: Suppress verbose output.
 
@@ -119,6 +120,18 @@ kaggle competitions download <COMPETITION> [options]
     kaggle competitions download titanic -f test.csv -p tost
     ```
 
+3.  Download a file that lives in a folder inside the competition data. The file is written to `data/kaggle_evaluation/rsna_gateway.py`:
+
+    ```bash
+    kaggle competitions download rsna-intracranial-aneurysm-detection -f kaggle_evaluation/rsna_gateway.py -p data
+    ```
+
+4.  Download all files for the "titanic" competition into `data` and extract them, leaving no zip behind:
+
+    ```bash
+    kaggle competitions download titanic -p data --unzip
+    ```
+
 **Purpose:**
 
 This command allows you to get the necessary data files for a competition onto your local machine.
@@ -145,6 +158,10 @@ kaggle competitions submit <COMPETITION> -f <FILE_NAME> -m <MESSAGE> [options]
 *   `-v, --version <VERSION>`: Version of the kernel to submit (e.g. `2`).
 *   `-q, --quiet`: Suppress verbose output.
 *   `--sandbox`: Mark submission as a sandbox submission (competition hosts/admins only).
+*   `--wait [SECONDS]`: Wait for the submission to finish scoring, printing the public score when done. Optionally pass a timeout in seconds (`0` or no value = wait up to 12 hours, the maximum notebook runtime). Exits non-zero if scoring fails or the timeout is reached.
+*   `--poll-interval <SECONDS>`: Maximum seconds between status polls while waiting (default: `60`, minimum: `5`). Polling starts at 5s and increases automatically.
+
+On a successful submission the command prints the numeric submission ref, e.g. `Submission ref: 12345678`. You can look that submission up later with [`kaggle competitions submission`](#kaggle-competitions-submission).
 
 **Example: Standard (not code) competition:**
 
@@ -162,10 +179,67 @@ Submit the `submission.csv` produced by version `3` of your `<YOUR_USERNAME>/rsn
 kaggle competitions submit rsna-2024-lumbar-spine-degenerative-classification -f submission.csv -k <YOUR_USERNAME>/rsna-submission -v 3 -m "Test message"
 ```
 
+**Example: Submit and wait for the score (useful in CI):**
+
+Submit and block until scoring finishes (up to a 10-minute timeout), then print the public score:
+
+```bash
+kaggle competitions submit house-prices-advanced-regression-techniques -f sample_submission.csv -m "CI run" --wait 600
+```
+
+The command exits `0` once the submission is scored and non-zero if scoring fails or the timeout is reached, so it can gate a pipeline.
+
 **Purpose:**
 
 Use this command to upload your predictions or code to a competition for scoring.
 
+## `kaggle competitions submission`
+
+Shows the status and score of a single submission by its numeric ref (as printed by `kaggle competitions submit`). When a submission failed to score, the reason is shown as well.
+
+**Usage:**
+
+```bash
+kaggle competitions submission <SUBMISSION_REF>
+```
+
+**Arguments:**
+
+*   `<SUBMISSION_REF>`: The numeric submission ref printed by `kaggle competitions submit`.
+
+**Example:**
+
+```bash
+kaggle competitions submission 12345678
+```
+
+Output:
+
+```
+Submission Ref:  12345678
+Status:          COMPLETE
+Public Score:    0.98765
+Private Score:
+Description:     Test message
+Submission Date: 2026-07-19 12:00:00
+```
+
+A submission that failed to score also reports why:
+
+```
+Submission Ref:  12345679
+Status:          ERROR
+Error:           Evaluation Exception: Submission must have 418 rows
+Public Score:
+Private Score:
+Description:     Test message
+Submission Date: 2026-07-19 12:00:00
+```
+
+**Purpose:**
+
+Use this command to check whether a submission has finished scoring and to read its public score — for example, after submitting without `--wait`, or from a script polling for results.
+
 ## `kaggle competitions submissions`
 
 Shows your past submissions for a competition.
@@ -197,6 +271,38 @@ kaggle competitions submissions house-prices-advanced-regression-techniques -v -
 
 This command allows you to review your previous submission attempts and their scores.
 
+## `kaggle competitions submission-download`
+
+Downloads the submitted file for a single submission by its numeric id.
+
+**Usage:**
+
+```bash
+kaggle competitions submission-download <SUBMISSION_ID> [options]
+```
+
+**Arguments:**
+
+*   `<SUBMISSION_ID>`: The numeric submission id printed by `kaggle competitions submit`, or listed by `kaggle competitions submissions <COMPETITION>`.
+
+**Options:**
+
+*   `-p, --path <PATH>`: Folder to download the file to. Defaults to the current working directory's Kaggle download location.
+*   `-o, --force`: Download even if a local copy already exists (skips the up-to-date check).
+*   `-q, --quiet`: Suppress verbose output.
+
+**Example:**
+
+Download the file for submission `12345678` into `./subs`:
+
+```bash
+kaggle competitions submission-download 12345678 -p ./subs
+```
+
+**Purpose:**
+
+Use this command to retrieve the exact file you (or a teammate) submitted — for example, to inspect an old submission or reproduce a scored result.
+
 ## `kaggle competitions leaderboard`
 
 Gets competition leaderboard information.

{kaggle-2.2.4 → kaggle-2.2.5}/docs/datasets.md

@@ -99,10 +99,10 @@ kaggle datasets download <DATASET> [options]
 
 **Options:**
 
-*   `-f, --file <FILE_NAME>`: Specific file to download (downloads all if not specified).
+*   `-f, --file <FILE_NAME>`: Specific file to download (downloads all if not specified). A file inside a folder, such as `train/labels.csv`, keeps that folder under the download path.
 *   `-p, --path <PATH>`: Folder to download files to (defaults to current directory).
 *   `-w, --wp`: Download files to the current working path.
-*   `--unzip`: Unzip the downloaded file (deletes the .zip file afterwards).
+*   `--unzip`: Unzip the downloaded file (deletes the .zip file afterwards). With `-f`, large files are served inside a zip archive of the same name, and this extracts the file from it.
 *   `-o, --force`: Force download, overwriting existing files.
 *   `-q, --quiet`: Suppress verbose output.
 
@@ -126,6 +126,18 @@ kaggle datasets download <DATASET> [options]
     kaggle datasets download goefft/public-datasets-with-file-types-and-columns -f dataset_results.csv -w -q -o
     ```
 
+4.  Download a file that lives in a folder inside the dataset. The file is written to `data/WICAgencies2014ytd/Food_Costs.csv`:
+
+    ```bash
+    kaggle datasets download jpmiller/publicassistance -f WICAgencies2014ytd/Food_Costs.csv -p data
+    ```
+
+5.  Download a single large file and extract it. `creditcard.csv` is served as `creditcard.csv.zip`, so without `--unzip` the archive is what lands on disk:
+
+    ```bash
+    kaggle datasets download mlg-ulb/creditcardfraud -f creditcard.csv -p data --unzip
+    ```
+
 **Purpose:**
 
 This command allows you to retrieve dataset files for local use.

{kaggle-2.2.4 → kaggle-2.2.5}/docs/index.rst

@@ -22,4 +22,5 @@ kaggle-cli documentation
    model_instances
    model_instances_versions
    benchmarks
+   search
    tutorials

{kaggle-2.2.4 → kaggle-2.2.5}/docs/kernels.md

@@ -76,7 +76,7 @@ kaggle kernels files <KERNEL> [options]
 
 **Arguments:**
 
-*   `<KERNEL>`: Kernel URL suffix (format: `owner/kernel-slug`, e.g., `kerneler/sqlite-global-default`).
+*   `<KERNEL>`: Kernel URL suffix (format: `owner/kernel-slug` or `owner/kernel-slug/version`, e.g., `kerneler/sqlite-global-default` or `kerneler/sqlite-global-default/2`).
 
 **Options:**
 
@@ -124,7 +124,7 @@ This command creates a template `kernel-metadata.json` file. You need to edit th
 
 ## `kaggle kernels push`
 
-Pushes new code/notebook and metadata to a kernel, then runs the kernel.
+Pushes new code/notebook and metadata to a kernel, then runs the kernel. Pass `--no-run` to save a new version without running it.
 
 **Usage:**
 
@@ -134,9 +134,10 @@ kaggle kernels push -p <FOLDER_PATH> [options]
 
 **Options:**
 
-*   `--accelerator <ACCELERATOR_ID>`: ID name of the accelerator to use during the run. E.g. "NvidiaTeslaP100" (aka default GPU), "NvidiaTeslaT4", "TpuV6E8".
+*   `--accelerator <ACCELERATOR_ID>`: ID name of the accelerator to use during the run. E.g. "NvidiaTeslaT4" (GPU T4 ×2, default GPU), "NvidiaL4", "TpuV5E8" (TPU v5e-8), "TpuV6E8".
 *   `-p, --path <FOLDER_PATH>`: Path to the folder containing the kernel file (e.g., `.ipynb`, `.Rmd`, `.py`) and the `kernel-metadata.json` file (defaults to the current directory).
 *   `-t, --timeout <SECONDS>`: Maximum run time in seconds.
+*   `--no-run`: Save a new version without executing the notebook, the equivalent of Quick Save in the web UI. The version is created but no cell runs.
 
 **Example:**
 
@@ -146,20 +147,22 @@ Push the kernel from the `tests/kernel` folder (assuming it contains the kernel
 kaggle kernels push -p tests/kernel
 ```
 
+Save a new version without running it, for example after editing only a markdown cell:
+
+```bash
+kaggle kernels push -p tests/kernel --no-run
+```
+
 **Purpose:**
 
 This command uploads your local kernel file and its metadata to Kaggle. If the kernel specified in the metadata exists under your account, it will be updated. Otherwise, a new kernel will be created. After uploading, Kaggle will attempt to run the kernel.
 
-Accelerators available as of Feb 2026:
+Accelerators available as of Sep 2026:
 
-* NvidiaTeslaP100
-* TpuV38
-* NvidiaTeslaT4
-* NvidiaTeslaT4Highmem
-* Tpu1VmV38
+* NvidiaTeslaT4 (GPU T4 ×2)
 * NvidiaTeslaA100
 * NvidiaL4
-* TpuV5E8
+* TpuV5E8 (TPU v5e-8)
 * NvidiaL4X1
 * TpuV6E8
 * NvidiaH100
@@ -223,7 +226,7 @@ kaggle kernels output <KERNEL> [options]
 
 **Arguments:**
 
-*   `<KERNEL>`: Kernel URL suffix (e.g., `kerneler/using-google-bird-vocalization-model`).
+*   `<KERNEL>`: Kernel URL suffix (format: `owner/kernel-slug` or `owner/kernel-slug/version`, e.g., `kerneler/using-google-bird-vocalization-model` or `kerneler/using-google-bird-vocalization-model/2`). Without a version, the latest version's output is downloaded.
 
 **Options:**
 
@@ -266,6 +269,12 @@ Download files in smaller pages:
 kaggle kernels output <kernel> --page-size 50
 ```
 
+Download the output of version 2 instead of the latest version:
+
+```bash
+kaggle kernels output <kernel>/2
+```
+
 **Purpose:**
 
 Use this command to retrieve the files generated by a kernel run, such as submission files, processed data, or visualizations. By default, output downloads scan every available output page, so `--file-pattern` can match files beyond the first page. Use `--page-size` to control how many files are requested on each page, and use `--page-token` when you only want to download files from one specific page.
@@ -282,7 +291,7 @@ kaggle kernels status <KERNEL>
 
 **Arguments:**
 
-*   `<KERNEL>`: Kernel URL suffix (e.g., `kerneler/sqlite-global-default`).
+*   `<KERNEL>`: Kernel URL suffix (format: `owner/kernel-slug` or `owner/kernel-slug/version`, e.g., `kerneler/sqlite-global-default` or `kerneler/sqlite-global-default/2`).
 
 **Example:**
 

{kaggle-2.2.4 → kaggle-2.2.5}/docs/kernels_metadata.md

@@ -35,7 +35,7 @@ We currently support the following metadata fields for kernels.
 * `is_private`: Whether or not the kernel should be private. If not specified, will be `true`.
 * `enable_gpu`: Whether or not the kernel should run on a GPU. If not specified, will be `false`.
 * `enable_internet`: Whether or not the kernel should be able to access the internet. If not specified, will be `false`.
-* `machine_shape`: The accelerator/GPU type to use (e.g., `NvidiaTeslaT4`, `NvidiaTeslaP100`, or `Tpu1VmV38`).
+* `machine_shape`: The accelerator/GPU type to use (e.g., `NvidiaTeslaT4` for GPU T4 ×2, `NvidiaL4`, or `TpuV5E8` for TPU v5e-8).
 * `dataset_sources`: A list of dataset sources, specified as `"username/dataset-slug"`
 * `competition_sources`: A list of competition sources, specified as `"competition-slug"`
 * `kernel_sources`: A list of kernel sources, specified as `"username/kernel-slug"`

kaggle-2.2.5/docs/search.md

@@ -0,0 +1,76 @@
+# Search Command
+
+Search across all Kaggle content from a single command.
+
+## `kaggle search`
+
+Runs a unified search over Kaggle competitions, datasets, notebooks, models,
+users, and discussions and returns one ranked list of results. This is the
+cross-content equivalent of the per-command `-s/--search` flags (such as
+`kaggle datasets list --search`); use it when you don't yet know which content
+type you're looking for, or when you want results from several types at once.
+
+By default, `kaggle search` searches all CLI-supported content types
+(competition, dataset, notebook, model, user, discussion, benchmark) — not every
+backend document type (it excludes types the CLI cannot render usefully, such as
+comments, blogs, and courses). Result ordering uses the backend's canonical
+cross-content ranking. Use `--type` to narrow to specific types.
+
+**Usage:**
+
+```bash
+kaggle search "<query>" [options]
+```
+
+**Options:**
+
+*   `query`: The term(s) to search for (required).
+*   `-t, --type <TYPES>`: Restrict results to a comma-separated list of content types. Valid types: `competition`, `dataset`, `notebook`, `model`, `user`, `discussion`, `benchmark`. If omitted, all of these CLI-supported types are searched.
+*   `-m, --mine`: Restrict the search to your own content.
+*   `--sort-by <SORT_BY>`: Sort order. One of: `relevance` (default), `hotness`, `votes`, `dateCreated`, `dateUpdated`, `totalComments`, `lastViewed`.
+*   `--page-size <SIZE>`: Number of results to show on a page (default: 20, max: 100).
+*   `--page-token <TOKEN>`: Page token for results paging (printed as `Next Page Token = ...` at the top of a page when more results exist).
+*   `-v, --csv`: Print results in CSV format instead of a table.
+*   `--format <FORMAT>`: Print results in the selected format (`csv`, `table`, `json`). Supports field projection, e.g. `--format 'json(type,ref)'`.
+
+**Result columns:** `type`, `ref`, `title`, `owner`, `votes`. The `ref` column
+is the identifier you can pass to other commands — `owner/slug` for datasets,
+notebooks, and models; the bare slug for competitions and users.
+
+**Examples:**
+
+1.  Search everything for a term:
+
+    ```bash
+    kaggle search "protein folding"
+    ```
+
+2.  Search only datasets and models:
+
+    ```bash
+    kaggle search "diffusion" --type dataset,model
+    ```
+
+3.  Find users:
+
+    ```bash
+    kaggle search "andrew ng" --type user
+    ```
+
+4.  Search your own content, most recently updated first:
+
+    ```bash
+    kaggle search "baseline" --mine --sort-by dateUpdated
+    ```
+
+5.  Get machine-readable output:
+
+    ```bash
+    kaggle search "titanic" --format json
+    ```
+
+6.  Fetch the next page:
+
+    ```bash
+    kaggle search "llm" --page-size 50 --page-token <TOKEN>
+    ```

{kaggle-2.2.4 → kaggle-2.2.5}/pyproject.toml

@@ -24,9 +24,11 @@ keywords = ["Kaggle", "API"]
 requires-python = ">= 3.11"
 dependencies = [
     "bleach",
-    "kagglesdk >= 0.1.35, < 1.0", # sync with kagglehub
+    "kagglesdk >= 0.1.38, < 1.0", # sync with kagglehub
     "python-slugify",
     "requests",
+    # requests sets no certifi floor; older bundles trust the compromised emSign/eMudhra roots (GHSA-6q48-6c7w-9gw2).
+    "certifi >= 2026.10.19",
     "python-dateutil",
     "tqdm",
     "urllib3 >= 1.15.1",

{kaggle-2.2.4 → kaggle-2.2.5}/requirements.lock

@@ -10,8 +10,11 @@ attrs==26.1.0
     #   referencing
 bleach==6.3.0
     # via kaggle (pyproject.toml)
-certifi==2026.2.25
-    # via requests
+certifi==2026.10.19
+    # via
+    #   kaggle (pyproject.toml)
+    #   kagglesdk
+    #   requests
 charset-normalizer==3.4.6
     # via requests
 fastjsonschema==2.21.2
@@ -26,7 +29,7 @@ jupyter-core==5.9.1
     # via nbformat
 jupytext==1.19.1
     # via kaggle (pyproject.toml)
-kagglesdk==0.1.35
+kagglesdk==0.1.38
     # via kaggle (pyproject.toml)
 markdown-it-py==4.0.0
     # via