`set-env` command is deprecated and will be disabled soon

[sanjivpurohit]

Warning: The set-env command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

[Deleted user]

Thanks for letting me know :) I'll try to get it fixed soon, although this action should really not be used, much easier to just use $GITHUB_RUN_NUMBER now.

[Luke McGregor]

fixed by #14

[Luke McGregor]

@einaregilsson GITHUB_RUN_NUMBER doesn't work between different workflows (for example I have a different one for production), It also resets if you change the workflow name. GITHUB_RUN_ID does technically work, but it makes the ugliest version number possible (I think its a global run inside GitHub).

This action seems like a good compromise and give some control over the number

[Deleted user]

Fair point. I've published v3 which uses the updated way of setting env variables.

[Luke McGregor]

Cool thanks 👍