[ci] Replace set-output with GITHUB_OUTPUT in CI workflow

[Shiva953]

Fixes #669
This PR updates the CI workflow to replace the deprecated set-output commands with the new GITHUB_OUTPUT aligning with the latest changes in GitHub Actions.

[nemesifier]

Thanks @Shiva953, it looks good! Can you please provide a link to documentation regarding guidance migrating from the v2 to the v3 so we can double check?

[Shiva953]

Thanks @Shiva953, it looks good! Can you please provide a link to documentation regarding guidance migrating from the v2 to the v3 so we can double check?

These might be helpful
https://blog.eidinger.info/why-and-how-to-adopt-actionscheckoutv3-in-your-github-action-workflow
https://action-slack.netlify.app/migration/01-migrate-from-v2-to-v3/

[Shiva953]

@nemesifier any updates?

[nemesifier]

Sorry I lost this one from my radar, it should be good, what do you think @pandafy?
If you could rebase this on the latest master it would be helpful.

[pandafy]

@Shiva953 there's even v4 released now which used Node 20 as run-time.

https://github.com/actions/checkout/releases

Also, your linked pages were not very helpful. While mentioning any changes to underlying software, always provide references from the author (here GitHub) instead of articles.

E.g. I found this GitHub Blog for deprecation of set-output-name.
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

[Shiva953]

@Shiva953 there's even v4 released now which used Node 20 as run-time.

https://github.com/actions/checkout/releases

Also, your linked pages were not very helpful. While mentioning any changes to underlying software, always provide references from the author (here GitHub) instead of articles.

E.g. I found this GitHub Blog for deprecation of set-output-name. https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

got it, should I update it to v4 now? or it wouldn't make sense to update it manually each time

[Shiva953]

@pandafy any updates on this?

[nemesifier]

Also, your linked pages were not very helpful. While mentioning any changes to underlying software, always provide references from the author (here GitHub) instead of articles.

If you can that would be useful, so you can go ahead and update.

[Shiva953]

Also, your linked pages were not very helpful. While mentioning any changes to underlying software, always provide references from the author (here GitHub) instead of articles.

If you can that would be useful, so you can go ahead and update.

done.

[nemesifier]

Thanks @Shiva953 👍