Changes that will allow an array of envFile locations to be defined

[hildo]

Changes for issue #1505

[hildo]

Is there something I can do to help here? I don't understand why my changes would be causing these failures? It looks like it is related to this step?

[hildo]

It looks like the tool being used (vsce) needs NodeJS minimum version 20, and the build pipeline is using version 16?

Should Node be upgraded?

[hildo]

@jdneo @testforstephen I have attempted to update the CI build to use NodeJS version 20, with the hope that the build issues will be addressed. Could someone please approve the workflow so we can see if the changes were sufficient? If I understand correctly, the workflow approval is not Pull Request approval, and just running the pipeline against this feature branch.

[testforstephen]

please also update the envFile's type definition (should be ["array", "string"]) in package.json and description in package.nls.json

vscode-java-debug/package.json

Lines 488 to 489 in 4a903c4

	"envFile": {
	"type": "string",

And

vscode-java-debug/package.nls.json

Line 21 in 4a903c4

"java.debugger.launch.envFile.description": "Absolute path to a file containing environment variable definitions.",

[hildo]

Of course. Thank you for the review. Please let me know if I have done them correctly (I am not 100% sure that my changes to package.json are correct).

[testforstephen]

@hildo thanks for contribution.

[hildo]

Thank you!