The V4 steps had been marked as deprecated, which isn't quite right. There are newer steps available, and we do recommend using those, but V4 steps will continue to work as is if that's what users want to do.
The primary reason to move to the V5 steps is to get away from the auto download issues with the way the V4 steps detected the CLI version to automatically install. The new installer step allows better control of which SemVer boundaries a user want to lock to.
This PR changes the wording on the tasks and log messages, away from "deprecated" to just explaining that there are new versions of the tasks available.
The V4 steps had been marked as deprecated, which isn't quite right. There are newer steps available, and we do recommend using those, but V4 steps will continue to work as is if that's what users want to do.
The primary reason to move to the V5 steps is to get away from the auto download issues with the way the V4 steps detected the CLI version to automatically install. The new installer step allows better control of which SemVer boundaries a user want to lock to.
This PR changes the wording on the tasks and log messages, away from "deprecated" to just explaining that there are new versions of the tasks available.