| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
ci: attach provenance and SBOM attestations to the published container (#9398) * ci: attach provenance and SBOM attestations to the published container * ci: restore trailing newline at end of file --------- Co-authored-by: Lincoln Stein <lincoln.stein@gmail.com> | 1 个月前 | |
chore(github): update actions from deprecated node-20 versions (#9149) * chore(github): update actions from deprecated node-20 versions * fix(deploy-docs): use sync to address "no virtual environment found" --------- Co-authored-by: Kevin Turner <566360-keturn@users.noreply.gitlab.com> Co-authored-by: Alexander Eichhorn <alex@eichhorn.dev> Co-authored-by: Jonathan <34005131+JPPhoto@users.noreply.github.com> | 3 个月前 | |
chore(github): update actions from deprecated node-20 versions (#9149) * chore(github): update actions from deprecated node-20 versions * fix(deploy-docs): use sync to address "no virtual environment found" --------- Co-authored-by: Kevin Turner <566360-keturn@users.noreply.gitlab.com> Co-authored-by: Alexander Eichhorn <alex@eichhorn.dev> Co-authored-by: Jonathan <34005131+JPPhoto@users.noreply.github.com> | 3 个月前 | |
chore(github): update actions from deprecated node-20 versions (#9149) * chore(github): update actions from deprecated node-20 versions * fix(deploy-docs): use sync to address "no virtual environment found" --------- Co-authored-by: Kevin Turner <566360-keturn@users.noreply.gitlab.com> Co-authored-by: Alexander Eichhorn <alex@eichhorn.dev> Co-authored-by: Jonathan <34005131+JPPhoto@users.noreply.github.com> | 3 个月前 | |
chore(deps): remove dependency on Jupyter Notebook (and update uv) (#9409) * chore(deps): remove dependency on Jupyter Notebook * chore: update uv version to 0.11.28 (the version currently used by launcher) * chore(deps): use the global form of exclude-dependencies, and finish the uv bump Two fixes to how the Jupyter exclusion is declared and checked. 1. `exclude-dependencies = ["notebook"]` instead of the per-package table form. The table form is only understood by uv >= 0.11.25; on uv 0.10.0 - 0.11.24 it is a hard `Failed to parse: pyproject.toml / invalid type: map, expected a string`, which kills every uv command (sync, run, lock) for anyone whose uv is a few weeks old -- including contributors following the `uv sync --frozen` in docs/development/Setup/dev-environment.mdx. The global form has been accepted since uv 0.9.8, older uv merely warns and ignores it, and it resolves to exactly the same set: the regenerated lockfile differs only in the `[manifest] excludes` line, and the resolved package set is identical (63 packages removed, no version changes). No `required-version` is added on purpose -- it would hard-fail the uv 0.6.12 bundled in launcher <= 1.8.1, which today installs fine and, because the launcher syncs `--frozen`, already gets the trimmed environment straight from the lockfile. 2. typegen-checks.yml was the one workflow left on uv 0.6.10. That uv does not know `exclude-dependencies` at all, and on an unknown key it discards the *entire* `[tool.uv]` settings table -- `index-strategy = "unsafe-best-match"` and all four `[[tool.uv.index]]` definitions included -- with only a warning. Bumped to 0.11.28 like the other five. Verified with real uv binaries: `uv lock --locked` passes on 0.9.8, 0.10.3, 0.11.24, 0.11.25 and 0.11.28 (0.10.3 and 0.11.24 could not even parse the file before); `uv export --frozen` under 0.6.10 yields 131 packages with zero Jupyter-chain entries; scripts/check_aarch64_lock.py, check_pins.py and check_classifiers.py all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JdJB9VXy5o6o7tfY1JSBCM --------- Co-authored-by: Lincoln Stein <lincoln.stein@gmail.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> | 27 天前 | |
chore(github): update actions from deprecated node-20 versions (#9149) * chore(github): update actions from deprecated node-20 versions * fix(deploy-docs): use sync to address "no virtual environment found" --------- Co-authored-by: Kevin Turner <566360-keturn@users.noreply.gitlab.com> Co-authored-by: Alexander Eichhorn <alex@eichhorn.dev> Co-authored-by: Jonathan <34005131+JPPhoto@users.noreply.github.com> | 3 个月前 | |
chore(github): update actions from deprecated node-20 versions (#9149) * chore(github): update actions from deprecated node-20 versions * fix(deploy-docs): use sync to address "no virtual environment found" --------- Co-authored-by: Kevin Turner <566360-keturn@users.noreply.gitlab.com> Co-authored-by: Alexander Eichhorn <alex@eichhorn.dev> Co-authored-by: Jonathan <34005131+JPPhoto@users.noreply.github.com> | 3 个月前 | |
chore(github): update actions from deprecated node-20 versions (#9149) * chore(github): update actions from deprecated node-20 versions * fix(deploy-docs): use sync to address "no virtual environment found" --------- Co-authored-by: Kevin Turner <566360-keturn@users.noreply.gitlab.com> Co-authored-by: Alexander Eichhorn <alex@eichhorn.dev> Co-authored-by: Jonathan <34005131+JPPhoto@users.noreply.github.com> | 3 个月前 | |
chore(github): update actions from deprecated node-20 versions (#9149) * chore(github): update actions from deprecated node-20 versions * fix(deploy-docs): use sync to address "no virtual environment found" --------- Co-authored-by: Kevin Turner <566360-keturn@users.noreply.gitlab.com> Co-authored-by: Alexander Eichhorn <alex@eichhorn.dev> Co-authored-by: Jonathan <34005131+JPPhoto@users.noreply.github.com> | 3 个月前 | |
chore(deps): remove dependency on Jupyter Notebook (and update uv) (#9409) * chore(deps): remove dependency on Jupyter Notebook * chore: update uv version to 0.11.28 (the version currently used by launcher) * chore(deps): use the global form of exclude-dependencies, and finish the uv bump Two fixes to how the Jupyter exclusion is declared and checked. 1. `exclude-dependencies = ["notebook"]` instead of the per-package table form. The table form is only understood by uv >= 0.11.25; on uv 0.10.0 - 0.11.24 it is a hard `Failed to parse: pyproject.toml / invalid type: map, expected a string`, which kills every uv command (sync, run, lock) for anyone whose uv is a few weeks old -- including contributors following the `uv sync --frozen` in docs/development/Setup/dev-environment.mdx. The global form has been accepted since uv 0.9.8, older uv merely warns and ignores it, and it resolves to exactly the same set: the regenerated lockfile differs only in the `[manifest] excludes` line, and the resolved package set is identical (63 packages removed, no version changes). No `required-version` is added on purpose -- it would hard-fail the uv 0.6.12 bundled in launcher <= 1.8.1, which today installs fine and, because the launcher syncs `--frozen`, already gets the trimmed environment straight from the lockfile. 2. typegen-checks.yml was the one workflow left on uv 0.6.10. That uv does not know `exclude-dependencies` at all, and on an unknown key it discards the *entire* `[tool.uv]` settings table -- `index-strategy = "unsafe-best-match"` and all four `[[tool.uv.index]]` definitions included -- with only a warning. Bumped to 0.11.28 like the other five. Verified with real uv binaries: `uv lock --locked` passes on 0.9.8, 0.10.3, 0.11.24, 0.11.25 and 0.11.28 (0.10.3 and 0.11.24 could not even parse the file before); `uv export --frozen` under 0.6.10 yields 131 packages with zero Jupyter-chain entries; scripts/check_aarch64_lock.py, check_pins.py and check_classifiers.py all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JdJB9VXy5o6o7tfY1JSBCM --------- Co-authored-by: Lincoln Stein <lincoln.stein@gmail.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> | 27 天前 | |
chore(deps): remove dependency on Jupyter Notebook (and update uv) (#9409) * chore(deps): remove dependency on Jupyter Notebook * chore: update uv version to 0.11.28 (the version currently used by launcher) * chore(deps): use the global form of exclude-dependencies, and finish the uv bump Two fixes to how the Jupyter exclusion is declared and checked. 1. `exclude-dependencies = ["notebook"]` instead of the per-package table form. The table form is only understood by uv >= 0.11.25; on uv 0.10.0 - 0.11.24 it is a hard `Failed to parse: pyproject.toml / invalid type: map, expected a string`, which kills every uv command (sync, run, lock) for anyone whose uv is a few weeks old -- including contributors following the `uv sync --frozen` in docs/development/Setup/dev-environment.mdx. The global form has been accepted since uv 0.9.8, older uv merely warns and ignores it, and it resolves to exactly the same set: the regenerated lockfile differs only in the `[manifest] excludes` line, and the resolved package set is identical (63 packages removed, no version changes). No `required-version` is added on purpose -- it would hard-fail the uv 0.6.12 bundled in launcher <= 1.8.1, which today installs fine and, because the launcher syncs `--frozen`, already gets the trimmed environment straight from the lockfile. 2. typegen-checks.yml was the one workflow left on uv 0.6.10. That uv does not know `exclude-dependencies` at all, and on an unknown key it discards the *entire* `[tool.uv]` settings table -- `index-strategy = "unsafe-best-match"` and all four `[[tool.uv.index]]` definitions included -- with only a warning. Bumped to 0.11.28 like the other five. Verified with real uv binaries: `uv lock --locked` passes on 0.9.8, 0.10.3, 0.11.24, 0.11.25 and 0.11.28 (0.10.3 and 0.11.24 could not even parse the file before); `uv export --frozen` under 0.6.10 yields 131 packages with zero Jupyter-chain entries; scripts/check_aarch64_lock.py, check_pins.py and check_classifiers.py all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JdJB9VXy5o6o7tfY1JSBCM --------- Co-authored-by: Lincoln Stein <lincoln.stein@gmail.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> | 27 天前 | |
chore(deps): remove dependency on Jupyter Notebook (and update uv) (#9409) * chore(deps): remove dependency on Jupyter Notebook * chore: update uv version to 0.11.28 (the version currently used by launcher) * chore(deps): use the global form of exclude-dependencies, and finish the uv bump Two fixes to how the Jupyter exclusion is declared and checked. 1. `exclude-dependencies = ["notebook"]` instead of the per-package table form. The table form is only understood by uv >= 0.11.25; on uv 0.10.0 - 0.11.24 it is a hard `Failed to parse: pyproject.toml / invalid type: map, expected a string`, which kills every uv command (sync, run, lock) for anyone whose uv is a few weeks old -- including contributors following the `uv sync --frozen` in docs/development/Setup/dev-environment.mdx. The global form has been accepted since uv 0.9.8, older uv merely warns and ignores it, and it resolves to exactly the same set: the regenerated lockfile differs only in the `[manifest] excludes` line, and the resolved package set is identical (63 packages removed, no version changes). No `required-version` is added on purpose -- it would hard-fail the uv 0.6.12 bundled in launcher <= 1.8.1, which today installs fine and, because the launcher syncs `--frozen`, already gets the trimmed environment straight from the lockfile. 2. typegen-checks.yml was the one workflow left on uv 0.6.10. That uv does not know `exclude-dependencies` at all, and on an unknown key it discards the *entire* `[tool.uv]` settings table -- `index-strategy = "unsafe-best-match"` and all four `[[tool.uv.index]]` definitions included -- with only a warning. Bumped to 0.11.28 like the other five. Verified with real uv binaries: `uv lock --locked` passes on 0.9.8, 0.10.3, 0.11.24, 0.11.25 and 0.11.28 (0.10.3 and 0.11.24 could not even parse the file before); `uv export --frozen` under 0.6.10 yields 131 packages with zero Jupyter-chain entries; scripts/check_aarch64_lock.py, check_pins.py and check_classifiers.py all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JdJB9VXy5o6o7tfY1JSBCM --------- Co-authored-by: Lincoln Stein <lincoln.stein@gmail.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> | 27 天前 | |
chore(github): update actions from deprecated node-20 versions (#9149) * chore(github): update actions from deprecated node-20 versions * fix(deploy-docs): use sync to address "no virtual environment found" --------- Co-authored-by: Kevin Turner <566360-keturn@users.noreply.gitlab.com> Co-authored-by: Alexander Eichhorn <alex@eichhorn.dev> Co-authored-by: Jonathan <34005131+JPPhoto@users.noreply.github.com> | 3 个月前 | |
chore(deps): remove dependency on Jupyter Notebook (and update uv) (#9409) * chore(deps): remove dependency on Jupyter Notebook * chore: update uv version to 0.11.28 (the version currently used by launcher) * chore(deps): use the global form of exclude-dependencies, and finish the uv bump Two fixes to how the Jupyter exclusion is declared and checked. 1. `exclude-dependencies = ["notebook"]` instead of the per-package table form. The table form is only understood by uv >= 0.11.25; on uv 0.10.0 - 0.11.24 it is a hard `Failed to parse: pyproject.toml / invalid type: map, expected a string`, which kills every uv command (sync, run, lock) for anyone whose uv is a few weeks old -- including contributors following the `uv sync --frozen` in docs/development/Setup/dev-environment.mdx. The global form has been accepted since uv 0.9.8, older uv merely warns and ignores it, and it resolves to exactly the same set: the regenerated lockfile differs only in the `[manifest] excludes` line, and the resolved package set is identical (63 packages removed, no version changes). No `required-version` is added on purpose -- it would hard-fail the uv 0.6.12 bundled in launcher <= 1.8.1, which today installs fine and, because the launcher syncs `--frozen`, already gets the trimmed environment straight from the lockfile. 2. typegen-checks.yml was the one workflow left on uv 0.6.10. That uv does not know `exclude-dependencies` at all, and on an unknown key it discards the *entire* `[tool.uv]` settings table -- `index-strategy = "unsafe-best-match"` and all four `[[tool.uv.index]]` definitions included -- with only a warning. Bumped to 0.11.28 like the other five. Verified with real uv binaries: `uv lock --locked` passes on 0.9.8, 0.10.3, 0.11.24, 0.11.25 and 0.11.28 (0.10.3 and 0.11.24 could not even parse the file before); `uv export --frozen` under 0.6.10 yields 131 packages with zero Jupyter-chain entries; scripts/check_aarch64_lock.py, check_pins.py and check_classifiers.py all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JdJB9VXy5o6o7tfY1JSBCM --------- Co-authored-by: Lincoln Stein <lincoln.stein@gmail.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> | 27 天前 | |
chore(deps): remove dependency on Jupyter Notebook (and update uv) (#9409) * chore(deps): remove dependency on Jupyter Notebook * chore: update uv version to 0.11.28 (the version currently used by launcher) * chore(deps): use the global form of exclude-dependencies, and finish the uv bump Two fixes to how the Jupyter exclusion is declared and checked. 1. `exclude-dependencies = ["notebook"]` instead of the per-package table form. The table form is only understood by uv >= 0.11.25; on uv 0.10.0 - 0.11.24 it is a hard `Failed to parse: pyproject.toml / invalid type: map, expected a string`, which kills every uv command (sync, run, lock) for anyone whose uv is a few weeks old -- including contributors following the `uv sync --frozen` in docs/development/Setup/dev-environment.mdx. The global form has been accepted since uv 0.9.8, older uv merely warns and ignores it, and it resolves to exactly the same set: the regenerated lockfile differs only in the `[manifest] excludes` line, and the resolved package set is identical (63 packages removed, no version changes). No `required-version` is added on purpose -- it would hard-fail the uv 0.6.12 bundled in launcher <= 1.8.1, which today installs fine and, because the launcher syncs `--frozen`, already gets the trimmed environment straight from the lockfile. 2. typegen-checks.yml was the one workflow left on uv 0.6.10. That uv does not know `exclude-dependencies` at all, and on an unknown key it discards the *entire* `[tool.uv]` settings table -- `index-strategy = "unsafe-best-match"` and all four `[[tool.uv.index]]` definitions included -- with only a warning. Bumped to 0.11.28 like the other five. Verified with real uv binaries: `uv lock --locked` passes on 0.9.8, 0.10.3, 0.11.24, 0.11.25 and 0.11.28 (0.10.3 and 0.11.24 could not even parse the file before); `uv export --frozen` under 0.6.10 yields 131 packages with zero Jupyter-chain entries; scripts/check_aarch64_lock.py, check_pins.py and check_classifiers.py all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JdJB9VXy5o6o7tfY1JSBCM --------- Co-authored-by: Lincoln Stein <lincoln.stein@gmail.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> | 27 天前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 个月前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 27 天前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 27 天前 | ||
| 27 天前 | ||
| 27 天前 | ||
| 3 个月前 | ||
| 27 天前 | ||
| 27 天前 |