ci: dont need seperate upload workflow

kolonialno · Feb 5, 2024 · 69ec62c · 69ec62c
1 parent 0fac3af
commit 69ec62c
Show file tree

Hide file tree

Showing 5 changed files with 4 additions and 141 deletions.
diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.yml
@@ -23,11 +23,6 @@ jobs:
       - uses: google-github-actions/release-please-action@v4
         id: release
         with:
-          # When you use the repository's GITHUB_TOKEN to perform tasks, events such as 'on.release'
-          # use in the Upload artifacts workflow wont be triggered.
-          # This prevents you from accidentally creating recursive workflow runs.
-          # We needed to use either a PAT og a GitHub App.
-          # https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#triggering-a-workflow-from-a-workflow
-          token: ${{ secrets.TIENDABOT_ACCESS_TOKEN }}
+          token: ${{ secrets.GITHUB_TOKEN }}
           config-file: release-please-config.json
           manifest-file: .release-please-manifest.json
diff --git a/.github/workflows/release-upload-artifacts.yml b/.github/workflows/release-upload-artifacts.yml
diff --git a/.release-please-manifest.json b/.release-please-manifest.json
@@ -1,3 +1,3 @@
 {
-  ".": "4.3.1"
+  ".": "4.4.1"
 }
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,3 +1,4 @@
+<!--pytest-codeblocks:skipfile-->
 # CONTRIBUTING
 
 ## Set-up

diff --git a/release-please-config.json b/release-please-config.json
@@ -1,6 +1,6 @@
 {
   "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
-  "bootstrap-sha": "3c032c809f68f677d12fdac5557351cde40bffd7",
+  "bootstrap-sha": "8ed4b839a6c7808f551baea9284eb7e36be7ef58",
   "include-v-in-tag": false,
   "separate-pull-requests": true,
   "prerelease": true,