`FORCE` option unrecognized
wottpal opened this issue Β· 14 comments
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 ποΈ
@BetaHuhn Did you make sure to correctly deploy packaged versions to Github? I don't know the exact publishing process myself tbh.
Just preventing the bot to close this
push
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:
This is because it's not listed here (1.9.12
tag = latest release):
deploy-to-vercel-action/action.yml
Line 78 in 0f16bc3
But it is here (master
branch):
deploy-to-vercel-action/action.yml
Line 82 in 643bc80
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 π¦π