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

[Bug] Deprecations #70

Open
saliceti opened this issue Oct 18, 2022 · 4 comments
Open

[Bug] Deprecations #70

saliceti opened this issue Oct 18, 2022 · 4 comments
Labels
need-to-triage Requires investigation

Comments

@saliceti
Copy link

This should be updated or the action will stop working

node12

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: Azure/pipelines

set-output

The `set-output` command is deprecated 
and will be disabled soon. Please upgrade to using Environment Files. 
For more information see: 
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
@craigbroadman
Copy link

@tjcorr, @keifgwinn, @Josh-01 - is there any idea when this will be resolved as node 12 is deprecated?

@marcus1aleksand
Copy link

marcus1aleksand commented Nov 6, 2023

Not long ago, I ran into the same problem and noticed that this module wasn't being maintained so I forked it and fixed in the forked repo maintained by me. Now, it can be consumable in ver 1.4. I can also push something similar to a Liatrio repo. Here is the link for the fix: https://github.com/marcus1aleksand/adopipelines

Here is an use example:

- uses: marcus1aleksand/[email protected]
  with:
    azure-devops-project-url: 'https://dev.azure.com/organization/project-name'
    azure-pipeline-name: 'pipeline-name' # name of the Azure pipeline to be triggered
    azure-devops-token: '${{ secrets.AZURE_DEVOPS_TOKEN }}'
    azure-pipeline-variables:  '{"variable1": "value1", "variable2": "value2"}' # optional stringified json

@keifgwinn
Copy link
Contributor

keifgwinn commented Nov 6, 2023

@tjcorr, @keifgwinn, @Josh-01 - is there any idea when this will be resolved as node 12 is deprecated?

my pull request resolved this, the issue is they haven't re-tagged. You could change to use the commit reference f1fe65f to pull the version that is on node16

- uses: Azure/pipelines@f1fe65f3daf2f705ca49c37ef172109e3e7c0d8f I think would work

@cwp-sheal
Copy link

It would be really helpful to get this resolved @tjcorr, @keifgwinn, @Josh-01.
The fix is merged, just needs a new patch tag if that's at-all possible.
it's been two years since the last release and Node 12 is deprecated now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need-to-triage Requires investigation
Projects
None yet
Development

No branches or pull requests

5 participants