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

error 'manifest.filter is not a funcion' when using node-version with "lts/*" #1162

Open
2 of 5 tasks
giulianisanches opened this issue Nov 21, 2024 · 2 comments
Open
2 of 5 tasks
Assignees
Labels
bug Something isn't working

Comments

@giulianisanches
Copy link

Description:
I'm trying to install the latest LTS version using the syntax "lts/*" and getting the error manifest.filter is not a function. Using a different syntax, like 22.x works.

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: "lts/*"
          check-latest: true

Action version:
actions/setup-node@v4

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:
Default ones installed with ubuntu 20.04

Repro steps:
I just have an action like below, and it fails when I push to the wip branch:

name: Build

on:
  push:
    branches:
      - wip

jobs:
  build:
    environment: shared
    runs-on: [self-hosted]
    steps:
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: "lts/*"
          check-latest: true

Expected behavior:
I expect it to install the latest LTS version

Actual behavior:
build fails with the message manifest.filter is not a function

@giulianisanches giulianisanches added bug Something isn't working needs triage labels Nov 21, 2024
@priyagupta108
Copy link
Contributor

Hello @giulianisanches 👋,
Thank you for your report. We'll investigate the issue and get back to you with the details!

@gowridurgad
Copy link

gowridurgad commented Nov 27, 2024

Hi @giulianisanches, After replicating the issue based on the provided workflow, it appears that everything is functioning correctly, and we were able to install the latest LTS version without encountering any issues. Here's a screenshot for your reference. To help us further investigate the issue, could you please provide a link to the build or public repository where we can reproduce the issue?
Screenshot 2024-11-27 at 9 09 15 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants