Please convert output with latest environment files

[rsharma02-entrata]

Please check this-
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#environment-files

[mukunku]

Could you please explain a bit more in detail what should be changed? The github action doesn't use yaml to generate environment variables. It's all javascript. If you were worried about deprecated warnings try out v1.1.0 now.

[edlerd]

I think it refers to a warning, that set-output is deprecated. But this is only true, while inside a workflow yaml file. But in an action, it is actually fine to still use core.setOutput. Updating to the latest @actions/core version should fix it.

I found the same problem and the possible solution here: actions/toolkit#1218

[mukunku]

Thanks @edlerd . I bumped the @actions/core version to 1.10 and the warning went away. I updated the v1.1.0 release instead of publishing a new one.

[pmalek]

Hi @mukunku 👋

Isn't this still using @actions/core 1.9.1? As per:

• https://github.com/mukunku/tag-exists-action/blob/v1.2.0/package-lock.json#L12
• and https://github.com/mukunku/tag-exists-action/blob/v1.2.0/package.json#L21

?

[mukunku]

Hi @mukunku 👋

Isn't this still using @actions/core 1.9.1? As per:

* https://github.com/mukunku/tag-exists-action/blob/v1.2.0/package-lock.json#L12

* and https://github.com/mukunku/tag-exists-action/blob/v1.2.0/package.json#L21

?

Hey @pmalek,

I believe ^1.9.1 should still resolve to 1.10.0 . Not sure why npm didn't update the package.json to make 1.10.0 the minimum though.

I'm basing this on this article:

If you see ^1.0.2 it means to install version 1.0.2 or the latest minor or patch version such as 1.1.0.

[KevinRohn]

Please check the open PR.

It`s still not resolved.

I fixed it in this commit:
3e6a721

[pof-kevinbutto]

@mukunku thank you for this action!
any update on this though? I'm still getting the "set-output command is deprecated " warning