vercel-action icon indicating copy to clipboard operation
vercel-action copied to clipboard

This action make a deployment with github actions instead of Vercel builder.

Results 109 vercel-action issues
Sort by recently updated
recently updated
newest added

Provide good examples(or template) of: * Issue * Branch Name * Commit Message * Pull Request * etc. If above provided, it would be easy to contribute to this repository.

Type: Maintenance

``` Failed to resolve action download info. Error: Unable to resolve action `amondnet/[email protected]+3`, unable to find version `v19.0.1 3` ``` This is the attempt with quotes - doesn't work without...

Type: Bug
Priority: High

I'm getting this error when deploying using vercel-action. Don't know if anyone else ran into the same error. I was able to deploy in my local terminal using `now` cli....

Type: Bug
Priority: High

By using Password Protection, you can ensure that visitors of your Preview Deployments must enter a password in order to gain access.

Type: Feature

Github announced this deprecation here https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/. They say `@actions/[email protected]` and higher solve the issue, however, this action is using v1.2.6 https://github.com/amondnet/vercel-action/blob/master/package.json#L26.

There was idea to add `vercel-version` option but for some reason, it was abandoned during this pull request https://github.com/amondnet/vercel-action/pull/171#discussion_r920623523, this one implements it.

```bash Error: There was an error when attempting to execute the process '/opt/hostedtoolcache/node/16.17.0/x64/bin/npx'. This may indicate the process failed to start. Error: spawn /opt/hostedtoolcache/node/16.17.0/x64/bin/npx ENOENT ``` The action then fails...

Bumps [jszip](https://github.com/Stuk/jszip) from 3.2.2 to 3.10.1. Changelog Sourced from jszip's changelog. v3.10.1 2022-08-02 Add sponsorship files. If you appreciate the time spent maintaining JSZip then I would really appreciate your...

dependencies

The current `v25` tag points to `v25.0.0` instead of `v25.1.0`. A solution would be to add an action that updates the major version tag automatically.

When I use ci to trigger the action without changing any code, it will deploy successfully, but it will still show failure in ci: ```txt this is related issue or...