Use release workflow for GitHub releases only

Author: oceanusXXD

.github/workflows/release.yml

@@ -8,10 +8,8 @@ on:
 jobs:
   publish:
     runs-on: ubuntu-latest
-    environment: pypi
     permissions:
       contents: write
-      id-token: write
 
     steps:
       - name: Checkout
@@ -59,9 +57,6 @@ jobs:
               raise SystemExit(f"Missing release note file: {release_note}")
           PY
 
-      - name: Publish to PyPI
-        uses: pypa/gh-action-pypi-publish@release/v1
-
       - name: Create GitHub Release
         uses: softprops/action-gh-release@v2
         with:

docs/ci.md

@@ -17,7 +17,7 @@ Auto mode decides between full and incremental execution from:
 This repository includes checked-in workflows under `.github/workflows/`:
 
 - `ci.yml`: test matrix, build, metadata check, and install smoke test
-- `release.yml`: build, metadata check, and PyPI publish on version tags
+- `release.yml`: version validation, build, metadata check, and GitHub Release creation on version tags
 
 The README includes a sample consumer workflow for running `code2skill` inside another repository.
 

docs/release.md

@@ -52,19 +52,10 @@ For a test-version rehearsal, you can skip this section and keep the current ver
 This repository includes:
 
 - `.github/workflows/ci.yml`: unit tests plus package build and install smoke check
-- `.github/workflows/release.yml`: build, `twine check`, and PyPI publish on version tags
+- `.github/workflows/release.yml`: version validation, build, `twine check`, and GitHub Release creation on version tags
 
-The release workflow expects PyPI publishing to be configured for trusted publishing or equivalent repository credentials.
-
-For the checked-in GitHub Actions workflow, the trusted-publishing environment name is `pypi`.
-If PyPI does not have a matching trusted publisher for:
-
-- owner: `oceanusXXD`
-- repository: `code2skill`
-- workflow: `.github/workflows/release.yml`
-- environment: `pypi`
-
-then the `Publish to PyPI` step will fail even when build and metadata checks succeed.
+The checked-in release workflow is intentionally repository-focused. It does not publish to PyPI automatically.
+If you want package publishing later, treat that as a separate manual or dedicated workflow concern.
 
 ## Manual Release Safety Notes
 

docs/releases/v0.1.6.md

@@ -8,8 +8,8 @@ This release is a follow-up to `0.1.5` and is intended to complete the first suc
 
 - keeps the current CLI and Python package surface from `0.1.5`
 - publishes from the latest `main` branch state
-- uses the updated release workflow with the `pypi` environment configured for trusted publishing
+- uses the updated release workflow for version validation, build checks, and GitHub Release creation without automatic PyPI publishing
 
 ## Result
 
-If the repository's trusted publisher is configured correctly on PyPI, this version should be the first fully successful GitHub Actions release in the new workflow line.
+This version is intended to be the first successful GitHub Actions release in the new repository-focused workflow line.