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

Set engines in package.json #946

Closed
JamieMagee opened this issue Jun 12, 2023 · 4 comments
Closed

Set engines in package.json #946

JamieMagee opened this issue Jun 12, 2023 · 4 comments

Comments

@JamieMagee
Copy link
Member

Environment

azure-pipelines-task-lib version: 4.3.1

Issue Description

It's not explicit what version of Node is supported when using the azure-pipelines-task-lib Node library. The dependency on @types/node version 16.x implies that version 4.x supports Node 16 only, but adding the engines property would make it explicit.

Expected behaviour

azure-pipelines-task-lib should explicitly state the versions of Node it supports

Actual behaviour

azure-pipelines-task-lib doesn't explicitly state what versions of Node it supports

Steps to reproduce

N/A

Logs

N/A

@github-actions
Copy link

This issue has had no activity in 90 days. Please comment if it is not actually stale

@github-actions github-actions bot added the stale label Sep 11, 2023
@JamieMagee
Copy link
Member Author

Not stale

Copy link

This issue has had no activity in 90 days. Please comment if it is not actually stale

@JamieMagee
Copy link
Member Author

Still not stale

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

No branches or pull requests

2 participants