Publish package to multiple registries

Is your feature request related to a problem? Please describe. When I added ability to select package registry (npm or github #599), I realize that will be nice to support publishing to both of them.

But ShipJS cant do this 😔

Describe the solution you’d like First solution that I figure out is add --publishOnly flag to trigger command. With that flag I can easily configurate github actions, will be like:

steps:
    # clone repo and checkout master 
  - uses: actions/checkout@master
    with:
      ref: master

    # setup node and npm with npmjs registry
  - uses: actions/setup-node@master
    with:
      registry-url: "https://registry.npmjs.org"
    
    # install shipjs and other dependencies
  - run: |
      if [ -f "yarn.lock" ]; then
        yarn install
      else
        npm install
      fi

    # trigger first release with all stuff
  - run: npm run release:trigger
    env:
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      NODE_AUTH_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
      SLACK_INCOMING_HOOK: ${{ secrets.SLACK_INCOMING_HOOK }}
  
    # setup node and npm with github registry
  - uses: actions/setup-node@master
    with:
      registry-url: "https://npm.pkg.github.com"
    
    # trigger second release that only publish package to registry
  - run: npm run release:trigger -- --publishOnly
    env:
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Describe alternatives you’ve considered I don’t know any alternatives. @eunjae-lee what do you think about that? May be you offer better solution for this case.

[eunjae-lee]

Hi @jeetiss ,

I’m not sure about this and the related PR #599. When we get enough of request, we can bake this in the setup command then. For now, I will close this issue and the PR.

Feel free to open them again if you want to continue to discuss on this 🙂

[eunjae-lee]

@jeetiss oh actually I meant yarn publish.

➜ yarn publish --help

  Usage: yarn publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>]

...

    --registry <url>                    override configuration registry

In my head, this will likely work:

NPM_AUTH_TOKEN=$GITHUB_TOKEN yarn publish --registry https://npm.pkg.github.com

If that is possible, I guess we can just document this and leave it to users.