semantic-release tries to fetch from old origin after renaming repo

[tjoskar]

Hi,

I have been using semantic-release in a GitHub action for some time now and it has been working great.

I have been using the following config:

- name: 📦 Semantic Release
  uses: cycjimmy/semantic-release-action@v2
  id: semantic
  with:
    semantic_version: 17.3.7
    extra_plugins: |
      @semantic-release/changelog@5.0.0
      @semantic-release/git@9.0.0
    env:
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

A few days ago I wanted to move our code to a new repo so I changed the origin and punched the code to the new repo:

git remote set-url origin git@github.com:new-repo.git
git push -f

But after that, I'm getting the following error:
(I have replaced the old repo name with "old-repo")

[7:41:07 AM] [semantic-release] › ℹ  Running semantic-release version 17.3.7
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/npm"
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/github"
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/npm"
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/npm"
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/github"
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/npm"
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/github"
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/github"
[7:41:07 AM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/github"
[7:41:08 AM] [semantic-release] › ✖  An error occurred while running semantic-release: Error: Command failed with exit code 128: git ls-remote --heads https://x-access-token:[secure]@github.com/old-repo.git
remote: Repository not found.
fatal: repository 'https://github.com/old-repo.git/' not found
    at makeError (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/execa/lib/error.js:60:11)
    at handlePromise (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/execa/index.js:118:26)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async getBranches (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/semantic-release/lib/git.js:66:11)
    at async module.exports (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/semantic-release/lib/branches/expand.js:6:23)
    at async module.exports (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/semantic-release/lib/branches/index.js:14:26)
    at async run (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/semantic-release/index.js:57:22)
    at async module.exports (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/node_modules/semantic-release/index.js:260:22)
    at async release (/home/runner/work/_actions/cycjimmy/semantic-release-action/v2/src/index.js:25:18) ***
  shortMessage: 'Command failed with exit code 128: git ls-remote --heads https://x-access-token:[secure]@github.com/old-repo.git',
  command: 'git ls-remote --heads https://x-access-token:[secure]@github.com/old-repo.git',
  escapedCommand: 'git ls-remote --heads "https://x-access-token:[secure]@github.com/old-repo.git"',
  exitCode: 128,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr: 'remote: Repository not found.\n' +
    "fatal: repository 'https://github.com/old-repo.git/' not found",
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
***
Error: Error: Command failed with exit code 128: git ls-remote --heads ***github.com/old-repo.git
remote: Repository not found.
fatal: repository 'https://github.com/old-repo.git/' not found

I understand that the github action is not part of this organization but it looks like the error comes from the @semantic-release/github plugin.

Why do the plugin still tries to fetch the old repo? Where is that information stored?

Thanks!

[travi]

You most likely need to update the repository property in your package.json

[tjoskar]

🤦

Thank you!