After a lot of thought and searching the docs of popular CI services (Azure Pipelines, AppVeyor, TravisCI, GitLab CI/CD, CircleCi) I come to the conclusion that the following should be supported:

# shorthand of the latest version of node
- node:
    alias:
        - ' '
        - current (?)
        - latest  (?)

# shorthand of node version 4
- argon:
    alias:
        - Argon

# shorthand of node version 6
- boron:
    alias:
        - Boron

# shorthand of node version 8
- carbon:
    alias:
        - Carbon

# shorthand of node version 10
- dubnium:
    alias:
        - Dubnium

# shorthand of node version 12
- erbium (?):
    alias:
        - Erbium

Those with a question mark are cases that I like to discuss with you.

node is used as a shorthand in TravisCI and ' ' in AppVeyor. Should we also support those or are we going with our own shorthand like latest?
Erbium is pending and can't be yet automated. I'm just mentioning it here as a placeholder.

From my POV lts/* should not be a choice, since the GitHub (Azure Pipelines) matrix.node-version property actually executes an iteration of the values specified, passing a single value of the version each time to create an instance.
lts/* resolves to multiple node versions that can't be interpreted into firing up multiple instances.

Similarly lts=dubnium should not be a choice either, simply specifying dubnium should suffice.

I'm not sure if lts should be a choice either. Which node version should lts point to?

Support aliases like LTS #26

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions