# Generated SBOM files will now include a package URL when a manifest file includes a range

DevFeed: [Generated SBOM files will now include a package URL when a manifest file includes a range](<https://devfeed.tech/articles/generated-sbom-files-will-now-include-a-package-url-when-a-manifest-file-includes-a-range-73084.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2024-06-11-generated-sbom-files-will-now-include-a-package-url-when-a-manifest-file-includes-a-range>)

Author: Allison

Published: 2024-06-11T16:24:38Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [image manifest](<https://devfeed.tech/topics/image-manifest.md>)

Tags: [include](<https://devfeed.tech/tags/include.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [package-url](<https://devfeed.tech/tags/package-url.md>), [range](<https://devfeed.tech/tags/range.md>), [sbom](<https://devfeed.tech/tags/sbom.md>)

## AI overview

GitHub updated its SBOM generation so package URLs are included when a manifest references a package version range. The optional version field is omitted in that case, yielding more complete SBOM data to help users identify packages in their repositories.

## Source excerpt

Until this release, when a manifest file included a version range of a package (e.g. version < 3), when GitHub generated an SBOM for that package, it would not include...