Refactor publish commands in CI workflows to remove provenance flag

- Updated publish-python-sdk.yml and release-python-sdk.yml to remove the --provenance flag from the uv publish command, simplifying the publishing process.
- Adjusted the SBOM verification command in release-python-sdk.yml to directly use the github.ref_name variable for improved accuracy.

Author: NiveditJain

.github/workflows/publish-python-sdk.yml

@@ -146,10 +146,10 @@ jobs:
             exit 0
           elif [ "$HTTP_STATUS" = "404" ]; then
             echo "Version $VERSION not found on PyPI. Proceeding with publish."
-            uv publish --provenance
+            uv publish
           else
             echo "Unexpected HTTP status $HTTP_STATUS when checking PyPI. Proceeding with publish."
-            uv publish --provenance
+            uv publish
           fi
 
       - name: Upload SBOM artifacts

.github/workflows/release-python-sdk.yml

@@ -175,13 +175,13 @@ jobs:
           echo "You can verify this package's provenance on PyPI using:" >> sbom-summary.md
           echo '```bash' >> sbom-summary.md
           echo 'pip install sigstore' >> sbom-summary.md
-          echo 'python -m sigstore verify --bundle <bundle-file> exospherehost==${{ startsWith(github.ref_name, 'v') && substring(github.ref_name, 1) || github.ref_name }}' >> sbom-summary.md
+          echo 'python -m sigstore verify --bundle <bundle-file> exospherehost==${{ github.ref_name }}' >> sbom-summary.md
           echo '```' >> sbom-summary.md
 
       - run: uv build
 
       - name: Publish to PyPI with provenance
-        run: uv publish --provenance
+        run: uv publish
 
       - name: Upload SBOM artifacts
         uses: actions/upload-artifact@v4

python-sdk/exospherehost/_version.py

@@ -1 +1 @@
-version = "0.0.2b8"
+version = "0.0.2b7"