Post Build Cleanup Warning on agent version 4.259.0

[RuneRJQL]

We have begun to notice warnings about the "Post Build Cleanup" task, we have tried to update agent to 4.259.0, and using both V3 and V4 of the task, but still same error.
I've copied the error message below.

##[warning]Task 'Post Build Cleanup' version 4 (PostBuildCleanup@4) is dependent on a Node version (16) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance

[HackproTm]

Confirm this warning message in ADO Agent 4.259.0 - Initial Job

[RuneRJQL]

Yes it is in "Initial Job" on 4.259.0

[ReneSchumacher]

Hi everyone,

we are currently looking for new owners of the three tasks Build Quality Checks, Create Work Item, and Post Build Cleanup inside Microsoft as the original authors are unable to keep supporting them. It is unlikely that someone will take over Post Build Cleanup. I'm thinking about making this task OSS, but I have to check the internal guidelines for this. It would then be moved from the Microsoft publisher to a 3rd party publisher.

That being said, I strongly encourage everyone to move away from the task towards our recommended workaround. The steps template we have provided contains a simple PowerShell script, which can also be used with a PowerShell task in classic pipelines.

[ps-tunnelsoft]

any news on this topic?

[ReneSchumacher]

Hi @ps-tunnelsoft, unfortunately, there's no new information to share. I have moved to different teams in the meantime and had to stop working on the extensions. So far, all my attempts to hand over the extensions to internal product teams have been in vain.

I would recommend to stop using Post Build Cleanup as there is a good alternative solution for YAML builds (see links above). For BQC and CWI I need to figure out how to make them public, so the community can take over (if someone wants to). This, however, requires a couple changes to the code (publisher information etc.) and the build processes. Currently, everything still is on Azure DevOps internally. Not sure when I'll have the time to do that.