Manifest publish fails for svg files

Core-Setup official builds are (still) failing due to:

  Starting build metadata push to the Build Asset Registry...
F:\vsagent\4\s\.packages\microsoft.dotnet.arcade.sdk\1.0.0-beta.19080.6\tools\SdkTasks\PublishBuildAssets.proj(36,5):
  error : Version could not be extracted from 'core-setup/Runtime/3.0.0-preview-27331-3/sharedfx_centos.7-x64_Release_version_badge.svg'

https://dev.azure.com/dnceng/internal/_build/results?buildId=84895

https://github.com/dotnet/arcade/issues/1842 added a ExcludeFromManifest feature that I tried to use in Core-Setup via https://github.com/dotnet/core-setup/pull/5037. The binlog shows that the metadata is set, but the generated manifest still has the SVGs and publish still fails.

Also in https://github.com/dotnet/arcade/issues/1842:

As a follow up, the error here was that when the split between arcade and arcade services happened we took an old version of Micosoft.DotNet.Maestro.Tasks which had no support for SVGs hence the error you were getting.

I’ve ported the correct version of the files so this does not happen again even though we have exclusion support

It doesn’t look like this fix took hold. 😕

@jcagme @chcosta @mmitche any ideas?

[dagood]

It works! Thanks.

[jcagme]

That’s correct. This should be hands-off for you since it looks like dependencies are flowing fine into core-setup. Or if it is high pri you could manually update the Arcade SDK version in global.json