Skip to content

Hard-coded node version incorrectly documented and incompatible with older projects #6

@coreyaus

Description

@coreyaus

Hey team

I've hit a small issue on a project that runs Node version 18 because this bit/init action actually hard-codes version 20 of Node here: https://github.com/bit-tasks/init/blob/v1/action.yml#L14-L17

The project README states that this GitHub Action uses Node version 18 here: https://github.com/bit-tasks/init?tab=readme-ov-file#github-actions

Questions

  1. Would it be possible to make that node-version configurable (the same way the ws-dir is configurable)?
  2. Or perhaps would it be possible to optionally skip the "Setup Node" step that uses actions/setup-node@v4 and hard-codes the Node version at version 20?
    • We already run our own set up Node step in our GitHub Actions anyway, so doing it at part of the bit/init action feels heavy-handed (unless perhaps it is only run if no existing Node install is detected or something like that)

Thanks for all your work and help - my team loves Bit and I appreciate your work maintaining this GH Action repository!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions