Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to resolve v4 #90

Open
cristianbote opened this issue Feb 1, 2023 · 3 comments
Open

Unable to resolve v4 #90

cristianbote opened this issue Feb 1, 2023 · 3 comments

Comments

@cristianbote
Copy link

Hey @Borales,

Tried the action for the first time toady and I am running into errors with v4 -- apparently. This is my action config:

name: name

on: deployment_status

jobs:
    tests:
        runs-on: ubuntu-latest
        steps:
            - uses: actions/checkout@v3
            
            - name: Set Node.js 18.x
              uses: actions/setup-node@v3
              with:
                node-version: 18.x

            - name: Run install
              uses: borales/actions-yarn@v3
              with:
                cmd: install
[name/tests]   ☁  git clone 'https://github.com/borales/actions-yarn' # ref=v4
[name/tests] Unable to resolve v4: unsupported object type
@zyguy-ankorstore
Copy link

Hi @cristianbote,
You can use the release 4.2.0 instead of 4.

  - name: Run install
    uses: borales/actions-yarn@v4.2.0
    with:
      cmd: install # will run `yarn install` command
  - name: Run TypeScript compiler
    uses: borales/actions-yarn@v4.2.0
    with:
      cmd: tsc # will run `yarn tsc` command
  - name: Build backend bundle
    uses: borales/actions-yarn@v4.2.0
    with:
      cmd: build:backend # will run `yarn build:backend` command

@Borales
Copy link
Owner

Borales commented Feb 1, 2023

@cristianbote yeah, a few people reported this issue on different threads, but I am unable to replicate this unfortunately.

I followed the suggested steps to keep the latest version git tagged with both tags. Hopefully, it will get resolved with the next release.

@matt-dale
Copy link

The workaround works well.
For visibility, it is possible to replicate the issue using act locally. https://github.com/nektos/act

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants