chore(main): release 0.0.6 (#6)

Instead lets set permissions in repository settings and see if that
works without the permissions settings in the workflow.

.github/release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.0.5"
+  ".": "0.0.6"
 }

.github/workflows/ci.yml

@@ -6,14 +6,9 @@ jobs:
   release-please:
     runs-on: ubuntu-latest
     if: github.ref == 'refs/heads/main'
-    permissions:
-      contents: write
     steps:
       - uses: jimeh/release-please-manifest-action@main
         id: release
-        with:
-          app-id: ${{ secrets.RELEASE_BOT_APP_ID }}
-          private-key: ${{ secrets.RELEASE_BOT_PRIVATE_KEY }}
       - name: Create/update MAJOR tag
         if: ${{ steps.release.outputs.release_created }}
         uses: richardsimko/update-tag@v1

CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## [0.0.6](https://github.com/jimeh/release-please-manifest-action/compare/v0.0.5...v0.0.6) (2023-05-08)
+
+
+### Features
+
+* **release:** remove use of GitHub App ([b60e27b](https://github.com/jimeh/release-please-manifest-action/commit/b60e27befea7298731468ae0a66eff098c362d86))
+
+
+### Bug Fixes
+
+* **release:** attempt to fix release job permissions ([c2d8586](https://github.com/jimeh/release-please-manifest-action/commit/c2d85862fdd1bdcb9b7b10dcb3d35d3d60f4afc6))
+* **release:** remove permissions block ([04d3b1e](https://github.com/jimeh/release-please-manifest-action/commit/04d3b1edbb4c7bd5f1b63b6bb3f65ca738ee1e52))
+
 ## [0.0.5](https://github.com/jimeh/release-please-manifest-action/compare/v0.0.4...v0.0.5) (2023-05-07)
 
 

README.md

@@ -66,7 +66,7 @@ on: push
 jobs:
   release-please:
     runs-on: ubuntu-latest
-    if: github.ref == 'refs/heads/main' || github.ref == 'refs/heads/master'
+    if: github.ref == 'refs/heads/main'
     steps:
       - uses: jimeh/release-please-manifest-action@v0
 ```
@@ -81,7 +81,7 @@ on: push
 jobs:
   release-please:
     runs-on: ubuntu-latest
-    if: github.ref == 'refs/heads/main' || github.ref == 'refs/heads/master'
+    if: github.ref == 'refs/heads/main'
     steps:
       - uses: google-github-actions/release-please-action@v3
         id: release-please
@@ -112,7 +112,7 @@ on: push
 jobs:
   release-please:
     runs-on: ubuntu-latest
-    if: github.ref == 'refs/heads/main' || github.ref == 'refs/heads/master'
+    if: github.ref == 'refs/heads/main'
     steps:
       - uses: jimeh/release-please-manifest-action@v0
         with:
@@ -129,7 +129,7 @@ on: push
 jobs:
   release-please:
     runs-on: ubuntu-latest
-    if: github.ref == 'refs/heads/main' || github.ref == 'refs/heads/master'
+    if: github.ref == 'refs/heads/main'
     steps:
       - uses: google-github-actions/release-please-action@v3
         id: release-please
@@ -162,7 +162,7 @@ Below we assume you have already setup `RELEASE_BOT_APP_ID` and
 `RELEASE_BOT_PRIVATE_KEY` secrets in the repository or organization.
 
 To set the private key secret, it is easiest to base64 encode the contents of
-`*.pem` file you get from the GitHub App's configuration page. The base64
+the `*.pem` file you get from the GitHub App's configuration page. The base64
 encoded string should not have any line-breaks.
 
 <!-- x-release-please-start-major -->
@@ -172,7 +172,7 @@ on: push
 jobs:
   release-please:
     runs-on: ubuntu-latest
-    if: github.ref == 'refs/heads/main' || github.ref == 'refs/heads/master'
+    if: github.ref == 'refs/heads/main'
     steps:
       - uses: jimeh/release-please-manifest-action@v0
         with:
@@ -190,7 +190,7 @@ on: push
 jobs:
   release-please:
     runs-on: ubuntu-latest
-    if: github.ref == 'refs/heads/main' || github.ref == 'refs/heads/master'
+    if: github.ref == 'refs/heads/main'
     steps:
       - uses: tibdex/github-app-token@v1
         id: github-app-token