Microsoft is moving modules such as PNP.PowerShell to require PowerShell 7.2 or higher.  Current version is 7.3.6.  My company has many scripts that write to SharePoint that are deployed via Bamboo.  The only work around is to have bamboo launch PowerShell.exe to then run PWSH.EXE and provide it the argument of a file to execute.  Doing this will mean that our log files will only show that a launcher script was executed but won't show the detailed logs of the second script.   This would also disable or render ineffective our versioning control in Bamboo. So for now anything we automate in Bamboo we are stuck with 5.1, at least for the time being. Please allow a choice to run PowerShell 5.1 or 7+

Travis is right, your description is incorrect.

Anyway we really need support for PowerShell 7 in Script task.

The description is not completely accurate.  The executable for v6 of PowerShell is also pwsh.exe (same as v7).  This means that Bamboo does not natively support any version of PowerShell since 5.1, which was released in January of 2017.

Please add a native way of using PowerShell v6+ in Bamboo's script task.  This could be accomplished using a new interpreter, or by allowing the target of the current PowerShell interpreter to be configured globally.