Profiles required on HDD when packaging, despite their existence in .forceignore

[triestelaporte]

I had some automatically created profiles surf down into my IDE from a SO, I didn't want these in a package, so very early on in the project I added this to my .forceignore:

force-app/main/default/profiles/Admin.profile
force-app/main/default/profiles/Custom%3A Marketing Profile.profile
force-app/main/default/profiles/Custom%3A Sales Profile.profile
force-app/main/default/profiles/Custom%3A Support Profile.profile
force-app/main/default/profiles/authtest Profile.profile

I was tired of seeing the files on my hard drive, so this morning I deleted them, knowing they were not packaged anyway.

Verified by examining all existing versions of package, none include the profiles

well, after I cleaned up my drive, I tried to make a new version, and I got this:

"message": "We couldn't create this package version because new components were added or existing components were deleted. Add components {Profile=[Custom%3A Support Profile, Custom%3A Marketing Profile, Admin, Custom%3A Sales Profile, authtest Profile]} back into the package version, and create the package version again.",

so I went back through my local history and grabbed the profiles, put them back and I ran the exact same command

"Status": "Success",

examine package after this, still does not contain profiles, as expected

[triestelaporte]

I think the profiles snuck into a version of the package at some point, but we set up ancestry to the previous version and killed the one that had the profiles once upon a time.

[eblazer]

This strategy works through 7.200.4. It appears that even though these profiles are included in the .forceignore file, they are still included in the package.xml sent to Salesforce but not actually packaged.

However starting with 7.200.5, my builds fail because they are now not included in the package.xml sent to Salesforce.

[github-actions]

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

[shetzel]

I believe this issue is now fixed and is similar to several newer issues such as:
#620
#2336

Profiles are searched within all package directories defined in sfdx-project.json. .forceignore does not apply in this search, which is by design. Only aspects of the profiles that are relevant to the metadata being packaged are used.