feat: add a deprecation warning when running Taskfiles with a v2 schema

[pd93]

Added a warning to the output when using a version: 2 schema. (This functionality was split out of #1198).

This might break things for people using v2 schemas in scripts if they update... we could stop output if the --silent flag is specified, but this might not stop it from breaking where some tasks have silent: true. Maybe we send the output to stderr instead? Thoughts welcome.

[andreynering]

Answering some of your questions:

• Yes, sending to stderr would be more appropriate, and mitigate possible breakage in scripts
• Yes, respecting the --silent flag be interesting. I wouldn't worry too much about silent: true set on tasks, though. v2 has very few users currently.

With these points addressed, I think this is good to go! 👍

[andreynering]

One more thing: this is worth a mention on the CHANGELOG, IMO.

Schema version 2 is now considered deprecated and scheduled to be removed in the next major release.

[pd93]

Yes, sending to stderr would be more appropriate, and mitigate possible breakage in scripts

Updated

Yes, respecting the --silent flag be interesting. I wouldn't worry too much about silent: true set on tasks, though. v2 has very few users currently.

It's actually kind of annoying to pass in the flags to the version checks function. I could move the check into the main function, but I think with this being output to stderr now, this should be necessary anymore?

One more thing: this is worth a mention on the CHANGELOG, IMO.

Ah yeah, I forgot to bring this change over from #1198. I've added it now, Thanks

[andreynering]

It's actually kind of annoying to pass in the flags to the version checks function. I could move the check into the main function, but I think with this being output to stderr now, this should be necessary anymore?

Agreed. No need to check --silent anymore.

CI broke. Probably easy to fix, just a matter of check stderr instead of stdout on the test, I believe.

EDIT: Fixed myself 🙂

[pd93]

CI broke. Probably easy to fix, just a matter of check stderr instead of stdout on the test, I believe.

Whoops, thank you 😛