pkg.pr.new: Push code release failed
Run pnpx pkg-pr-new publish
publish error
PR: ✔️ Push: ❌
logs
Error: publishing failed: {"url":"/publish","statusCode":403,"statusMessage":"","message":"Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment"}
at Object.run (/home/runner/.cache/pnpm/dlx/t6c2gbxqvfjjki5ut3q3wgvbcu/193b0ccbbac-a75/node_modules/.pnpm/pkg-pr-new@0.0.35/node_modules/pkg-pr-new/dist/index.js:3421:18)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async runCommand (/home/runner/.cache/pnpm/dlx/t6c2gbxqvfjjki5ut3q3wgvbcu/193b0ccbbac-a75/node_modules/.pnpm/pkg-pr-new@0.0.35/node_modules/pkg-pr-new/dist/index.js:2196:[16](https://github.com/element-plus/element-plus/actions/runs/12257309026/job/34194482729#step:10:17))
at async runCommand (/home/runner/.cache/pnpm/dlx/t6c2gbxqvfjjki5ut3q3wgvbcu/193b0ccbbac-a75/node_modules/.pnpm/pkg-pr-new@0.0.35/node_modules/pkg-pr-new/dist/index.js:2187:11)
at async runMain (/home/runner/.cache/pnpm/dlx/t6c2gbxqvfjjki5ut3q3wgvbcu/193b0ccbbac-a75/node_modules/.pnpm/pkg-pr-new@0.0.35/node_modules/pkg-pr-new/dist/index.js:2323:7)
Error: publishing failed: {"url":"/publish","statusCode":403,"statusMessage":"","message":"Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment"}
Error: Process completed with exit code 1.
https://github.com/element-plus/element-plus/blob/d9da5341d2ce82e2de630fc794aef0b524beb74c/.github/workflows/publish-pr-commit-pkg.yml#L51C11-L51C34 https://github.com/element-plus/element-plus/actions/runs/12257309026/job/34194482729
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 21 (13 by maintainers)
we made a release y’all!
I think you need the PR to be opened by an external person, then squash merge. This happened to me a few times: https://github.com/posva/unplugin-vue-router/actions/runs/12883975525/job/35919305398
Turning off comments with
--comment=offfixed it but no more comment 🥲i appreciate you!
On Thu, Feb 27, 2025 at 12:25 Eduardo San Martin Morote < @.***> wrote:
I tried it after seeing your comment. when pushing, I set
--comment=off, which indeed solved the problem. thanks!will release soon and see if it fixes the issue!
Ahh, i’ll see again.
On Wed, 11 Dec 2024, 10:37 btea, @.***> wrote: