GitHub Release goes to origin vs. upstream remote

We ran into an issue today where a release seemed to use different remotes than we expected.

We got tags in our “upstream” repo for 0.8.0 and 0.8.1:

https://github.com/Seneca-CDOT/telescope/releases

However, the actual GitHub Release went to the “origin” of the dev who ran it (cc @Silvyre):

https://github.com/Silvyre/telescope/releases/tag/0.8.1

I would have expected them both to go to the same repo.

Our release-it config looks like this:

{
  "hooks": {
    "before:init": ["npm run test-ci"]
  },
  "git": {
    "pushRepo": "upstream"
  },
  "github": {
    "release": true
  },
  "npm": {
    "publish": false
  }
}

With github I can specify the pushRepo but I don’t see anything like that in https://github.com/release-it/release-it/blob/master/docs/github-releases.md.

Is this a config error on our part, a misunderstanding about what is expected, or a bug in release-it?

Thanks for any guidance on this. We love release-it.

[webpro]

Alright, the feature is in v13.4.0

[webpro]

OK I guess that’s clearly two votes in favor of using the same remote 😃