CHANGES IN “CREATE DEPLOYABLE PACKAGE” V2.x – What it broke and how I fixed it

I noticed (in March 2025) that the “Create Deployable Package” step of my Dynamics 365 F&O build was suddenly producing a warning:

##[warning]New task version available. Please upgrade to latest to avoid disruption.

So, I upgraded from v0.* to v2.*. It didn’t look like I needed to change any configuration, so I kept it the same. Of note, my “Search pattern for binaries to package” (which I did not change) looked like this:

*
!*Test
$(Build.SourcesDirectory)\Metadata\ISVModel1
$(Build.SourcesDirectory)\Metadata\ISVModel2

After this change, I started getting an error on the “Create Deployable Package” step:

Starting: Create Deployable Package
==========================================================================
Task : Create Deployable Package
Description : Task to create a deployable package for Dynamics 365 for Finance and Operations
Version : 2.0.1801888
Author : Microsoft Corporation
Help : Review the Dynamics 365 for Finance and Operations [Developer Documentation](https://go.microsoft.com/fwlink/?linkid=2128586).
==========================================================================
D:\a\55\b\ISVmodel1
D:\a\55\b\ISVmodel2
D:\a\55\b\MyModel
D:\a\55\s\Metadata\ISVModel1
D:\a\55\s\Metadata\ISVModel2

##[error]Multiple entries with the same module folder name detected. Please modify the ‘Search Pattern’ field to ensure unique packages to avoid issues. Refer: https://go.microsoft.com/fwlink/?linkid=2128586#examples-of-search-patterns

Finishing: Create Deployable Package

Apparently, v0.* of this step has some logic for dealing with “duplicates” that differs from 2.*. I changed my “Search pattern for binaries to package” to just:

*
!*Test

After this change, the build completed and it deployed okay, but while my ISV models were included they missing all their labels. I experimented a bit, and landed on this:

*
!*Test
!ISVModel1
$(Build.SourcesDirectory)\Metadata\ISVModel1
!ISVModel2
$(Build.SourcesDirectory)\Metadata\ISVModel2

This last one seems to work.