BetaHuhn/deploy-to-vercel-action

`FORCE` option unrecognized

wottpal opened this issue Β· 14 comments

In the docs you have the FORCE option to skip vercels build cache. But when used throws the following warning:

Screen Shot 2022-07-02 at 15 45 26

Hey @wottpal it's actually me who made a PR for the force options, you need to specify the excat version of the action and the force options is available from the version 1.9.0 !

I have something like

    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: 16

      - name: 'Deploy'
        uses: BetaHuhn/deploy-to-vercel-action@v1.9.0

Hope it helps

Good to know, thanks for the follow-up :)
But may i ask why there is this limitation to specify the version specifically? Just out of curiosity.

Hey @wottpal
Not gonna lie, didn't take the time to look on the why, it was driving me crazy :D
But i should investigate on the why πŸ‘οΈ

It appears the option is missing in the file action.yml.

It also seems that no release since the v1.7.1 have made it to the Github Marketplace:

Capture d’écran 2022-08-26 aΜ€ 11 41 47

@BetaHuhn Did you make sure to correctly deploy packaged versions to Github? I don't know the exact publishing process myself tbh.

⚠️ This issue has not seen any activity in the past 2 months so I'm marking it as stale. I'll close it if it doesn't see any activity in the coming week.

Just preventing the bot to close this

⚠️ This issue has not seen any activity in the past 2 months so I'm marking it as stale. I'll close it if it doesn't see any activity in the coming week.

push

⚠️ This issue has not seen any activity in the past 2 months so I'm marking it as stale. I'll close it if it doesn't see any activity in the coming week.

push

Hey everyone, sorry for the very long delay!

The latest release should now be available on the Marketplace.

Did you make sure to correctly deploy packaged versions to Github?

The problem is that GitHub doesn't automatically publish the latest release to its Marketplace, you have to manually edit the release (without changing anything) for it to show up.

Hey everyone, sorry for the very long delay!

The latest release should now be available on the Marketplace.

Did you make sure to correctly deploy packaged versions to Github?

The problem is that GitHub doesn't automatically publish the latest release to its Marketplace, you have to manually edit the release (without changing anything) for it to show up.

Hey Maximilian, nice work with this project πŸ˜„ , we just faced the same problem as the original author of the issue described.

So I tried upgrading to the latest release but FORCE is still not supported:

image

This is because it's not listed here (1.9.12 tag = latest release):

But it is here (master branch):

So, I suppose that a simple release would fix it πŸ€” πŸ˜„

πŸŽ‰ This issue has been resolved in version 1.10.0 πŸŽ‰

The release is available on GitHub release

Your semantic-release bot πŸ“¦πŸš€