Updating to remove set-output

[nicleary]

Per Github set-output is now deprecated and should be removed.

[unfor19]

@nicleary sorry for the delay
Thanks

[maxlapides]

@unfor19 Thanks for merging this one! When do you think this update will be available on the GitHub Actions Marketplace? https://github.com/marketplace/actions/install-aws-cli-action

[unfor19]

@unfor19 Thanks for merging this one! When do you think this update will be available on the GitHub Actions Marketplace? https://github.com/marketplace/actions/install-aws-cli-action

Hi @maxlapides thanks for the reminder, I was out for a long time :)
I will create a new release later on today

Replies/inputs like this ticket are so valuable, thank you everyone for assisting with keeping this action up to date

Update- was able to create a release with my mobile device, so v1.0.4 includes this fix. Surprisingly, it was easy :)
I'll update the test action so the README won't show the red badge of failing tests, it bugs me

[maxlapides]

Hey thanks @unfor19! Really appreciate it. Quick question, I am discovering that when I update my workflow to use unfor19/install-aws-cli-action@v1.0.4, the workflow runs with the latest version of this action. But, when I use unfor19/install-aws-cli-action@v1, the workflow runs with an older version of this action. Is there some way to update the v1 tag also? I'm not sure how releasing to GitHub Marketplace works exactly!

[unfor19]

Thanks @maxlapides
You're right; setting v1 doesn't mean you're using the latest v1 (1.0.4), which is what I would expect.

Thanks for bringing it up, I'm reading about it, and I'll see if I can tweak the version to avoid modifying end-users workflows.

This seems to be like a good start - https://docs.github.com/en/actions/creating-actions/about-custom-actions#using-tags-for-release-management