You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 16e7f7e
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .agents/skills/release-openshell/SKILL.md
+4-15Lines changed: 4 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,8 +33,8 @@ Release creates `vX.Y.Z` at that exact commit, then rebuilds and publishes all
33
33
stable artifacts without rerunning qualification. Embedded versions change, so
34
34
stable artifacts are not byte-identical to the qualified prerelease. An existing
35
35
stable tag may be retried only if it already points to the selected commit. A retry
36
-
publishes only missing artifacts; published images, charts, release assets, npm,
37
-
and PyPI versions are kept, while the snap is uploaded again.
36
+
publishes only missing artifacts; published images, charts, release assets, and
37
+
npm versions are kept, while the snap is uploaded again.
38
38
Stable images are saved as OCI archives during the build and pushed under the
39
39
stable version tags during publication. Their SBOMs are verified before updating
40
40
`latest`; the qualified prerelease's commit-SHA image tags remain unchanged.
@@ -84,17 +84,6 @@ immutable version and advance latest only for a newer version.
84
84
85
85
Watch the stable release run and report its result.
86
86
87
-
## PyPI publishing
87
+
## Python SDK
88
88
89
-
Stable releases publish the Python wheel to PyPI from `wheel-publish.yml`, which the `publish-pypi` job in `release-publish.yml` calls after the GitHub Release is created. The workflow downloads the wheel from the stable GitHub Release, not a run's build artifact, and checks the stable tag's source commit and the wheel's release checksum. It uses Trusted Publishing with the `pypi` GitHub environment. PyPI matches the workflow file that contains the publishing job, so configure the `openshell` PyPI project's GitHub publisher with owner `NVIDIA`, repository `OpenShell`, workflow `wheel-publish.yml`, and environment `pypi`. No PyPI API token or GitLab trigger credentials are required.
90
-
91
-
The environment must allow the branch used to dispatch Release or `wheel-publish.yml`. For a support release, explicitly allow its support branch before dispatching. Required reviewers, if configured, must approve the PyPI job. An existing wheel on PyPI is skipped; PyPI does not allow replacing a published wheel.
92
-
93
-
If a stable release did not reach PyPI, publish the wheel without rerunning Release:
94
-
95
-
```shell
96
-
gh workflow run wheel-publish.yml -R NVIDIA/OpenShell --ref main \
Development and prerelease wheels remain GitHub Release assets and do not publish to PyPI.
89
+
Core no longer builds or publishes the Python SDK for releases. The stable, prerelease, and rolling `dev` GitHub Releases carry no wheel, and nothing in core publishes to PyPI. `openshell``0.1.7` is the last core-built wheel. From `0.1.8` on, [ai-openshell/sdk-python](https://github.com/ai-openshell/sdk-python) publishes `openshell` on the same day as each stable core release, once its update PR for the core tag merges.
echo "::error title=Python SDK moved::The Python SDK moved to https://github.com/ai-openshell/sdk-python. Drop the Python SDK changes from this PR and open SDK changes there. Regenerated bindings are not needed here; sdk-python regenerates them from core releases."
0 commit comments