You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a big discrepancy in the repository right now. The spec submodule is currently pinned to c398646, which is not on any branch or tag of purl-spec. It was done in #206 .
In the mean time, there is a v1.0.0 tag that is 204 commits ahead.
I use the current state of spec as the source of truth in #188 , but I think we need to pin the spec submodule to v1.0.0 and fix everything. Would you be interested in such a PR?
Activity
mjherzog commentedon Feb 2, 2026
Closing - see - package-url/purl-spec#644
mjherzog commentedon Feb 2, 2026
I should not have closed this Issue - I confused it with a similar purl-spec issue
kdeldycke commentedon Apr 23, 2026
There is a big discrepancy in the repository right now. The
specsubmodule is currently pinned toc398646, which is not on any branch or tag ofpurl-spec. It was done in #206 .It sits on an unmerged side branch, that has 11 commits not part of the
mainbranch at all: package-url/purl-spec@9b27957...c398646In the mean time, there is a
v1.0.0tag that is 204 commits ahead.I use the current state of
specas the source of truth in #188 , but I think we need to pin thespecsubmodule to v1.0.0 and fix everything. Would you be interested in such a PR?