breadcrumb-cli 0.1.0__tar.gz → 0.1.1__tar.gz

{breadcrumb_cli-0.1.0 → breadcrumb_cli-0.1.1}/.github/workflows/release.yml

@@ -5,6 +5,10 @@ on:
     tags:
       - v*
 
+permissions:
+  contents: write
+  packages: write
+
 jobs:
   test:
     runs-on: ubuntu-latest
@@ -95,6 +99,9 @@ jobs:
       
       - name: Create Release
         uses: softprops/action-gh-release@v2
+        env:
+          # Optional: set GH_TOKEN secret if the default GITHUB_TOKEN is restricted
+          GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
         with:
           files: release-artifacts/**/*
           draft: false

{breadcrumb_cli-0.1.0 → breadcrumb_cli-0.1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: breadcrumb-cli
-Version: 0.1.0
+Version: 0.1.1
 Summary: Chat with your codebase. Understand everything.
 Project-URL: Homepage, https://github.com/yourusername/breadcrumb
 Project-URL: Repository, https://github.com/yourusername/breadcrumb
@@ -123,6 +123,16 @@ Use TestPyPI when you want to validate packaging before a real release.
 
 This publishes to `https://test.pypi.org/legacy/` and does not create a GitHub Release.
 
+### Repository secrets for releases
+
+If the GitHub release step fails with a 403 ("Resource not accessible by integration"), add a Personal Access Token (PAT) as a repository secret and use it as a fallback for the release action.
+
+1. Create a PAT (classic) with `repo` scope or a fine-grained token that allows `Contents: Read & write` and `Releases` permissions.
+2. In your repository Settings → Secrets → Actions, add a new secret named `GH_TOKEN` with that token value.
+3. The release workflow will use `GITHUB_TOKEN` by default; if you prefer a PAT, update the `create-release` step to set `GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}` in the step's `env` block.
+
+This gives the release job permission to create releases and upload artifacts when organization policies or token scope prevent the default token from working.
+
 ### Option D: Docker
 ```bash
 docker run --rm \

{breadcrumb_cli-0.1.0 → breadcrumb_cli-0.1.1}/README.md

@@ -97,6 +97,16 @@ Use TestPyPI when you want to validate packaging before a real release.
 
 This publishes to `https://test.pypi.org/legacy/` and does not create a GitHub Release.
 
+### Repository secrets for releases
+
+If the GitHub release step fails with a 403 ("Resource not accessible by integration"), add a Personal Access Token (PAT) as a repository secret and use it as a fallback for the release action.
+
+1. Create a PAT (classic) with `repo` scope or a fine-grained token that allows `Contents: Read & write` and `Releases` permissions.
+2. In your repository Settings → Secrets → Actions, add a new secret named `GH_TOKEN` with that token value.
+3. The release workflow will use `GITHUB_TOKEN` by default; if you prefer a PAT, update the `create-release` step to set `GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}` in the step's `env` block.
+
+This gives the release job permission to create releases and upload artifacts when organization policies or token scope prevent the default token from working.
+
 ### Option D: Docker
 ```bash
 docker run --rm \

{breadcrumb_cli-0.1.0 → breadcrumb_cli-0.1.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "breadcrumb-cli"
-version = "0.1.0"
+version = "0.1.1"
 description = "Chat with your codebase. Understand everything."
 readme = "README.md"
 license = { text = "MIT" }