Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed step "publish" of plugin "@semantic-release/github" Resource not accessible by integration #2435

Closed
mikel21 opened this issue May 15, 2022 · 0 comments

Comments

@mikel21
Copy link

mikel21 commented May 15, 2022

Current behavior

Publish release to github return error on github action:

RequestError [HttpError]: Resource not accessible by integration
at /home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/@octokit/request/dist-node/index.js:86:21
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
status: 403

but locally
curl --user "mikel21" -X POST -H "Accept: application/vnd.github.v3+json" --data "{"tag_name":"v1.0.0","target_commitish":"dev","name":"v1.0.0","body":"Description of the release","draft":false,"prerelease":false,"generate_release_notes":false}" https://api.github.com/repos/Joiner2959/nagamaruki/releases
it's work

Expected behavior

Created release in github

Environment

  • semantic-release version: 19.0.2
  • CI environment: github
  • Plugins used: "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@semantic-release/github"
  • semantic-release configuration: module.exports = {
    branches: [
    "main",
    "dev"
    ],
    plugins: [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@semantic-release/github"
    ],
    repositoryUrl: "https://Joiner2959:ghp_blablabla@github.com/Joiner2959/nagamaruki"
    };
  • CI logs: image
@semantic-release semantic-release locked and limited conversation to collaborators May 16, 2022
@travi travi converted this issue into discussion #2436 May 16, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant