There have been signs that Microsoft considers sbom-tool EOL/deprecated, but no official announcement. Because I have been planning to expand my use of sbom-tool in build systems, I’d like to understand whether this EOL/deprecation is real.
The description of #1457 originally included this text:
sbom-tool is in EOL/deprecation — no new properties will be added.
Also, the initial commit of that pull request contained the following text in the .features/automapper-replacement-research.md file:
> **Context:** sbom-tool is being deprecated. We need to remove the AutoMapper dependency
> with minimal changes and minimal regression risk.
On the next day though, the description was edited to remove the mention of deprecation, and another commit was added to delete the .features/automapper-replacement-research.md file.
So far, EOL/deprecation has not been announced in README.md, and no versions of the Microsoft.Sbom.DotNetTool NuGet package have been marked as deprecated. #1235 disallowing external contributions would be consistent with EOL, though.
There have been signs that Microsoft considers sbom-tool EOL/deprecated, but no official announcement. Because I have been planning to expand my use of sbom-tool in build systems, I’d like to understand whether this EOL/deprecation is real.
The description of #1457 originally included this text:
Also, the initial commit of that pull request contained the following text in the
.features/automapper-replacement-research.mdfile:On the next day though, the description was edited to remove the mention of deprecation, and another commit was added to delete the
.features/automapper-replacement-research.mdfile.So far, EOL/deprecation has not been announced in README.md, and no versions of the Microsoft.Sbom.DotNetTool NuGet package have been marked as deprecated. #1235 disallowing external contributions would be consistent with EOL, though.