Enforce namespace restrictions

[milux]

Enforces namespace restrictions for all types that prohibit namespaces according to the JSON specs in https://github.com/package-url/purl-spec/tree/main/types at the time being. Selected via the following bash script:

for f in types/*.json; do
  if [[ "$(jq -r '.namespace_definition.requirement' "$f")" = 'prohibited' ]]; then
    echo "$f"
  fi
done

Further fixed the lowercased types. Identified via the following bash script and checked for "must be lowercased" note:

for f in types/*.json; do
  if [[ "$(jq -r '.namespace_definition.case_sensitive' "$f")" = 'false' ]] || [[ "$(jq -r .namespace_definition.is_case_sensitve "$f")" = 'false' ]]; then
    echo "$f"
    jq .namespace_definition.note "$f"
  fi
done

[ctron]

This is a breaking change. So you'd need to increment the version as well. Otherwise the CI should/will fail.

[ctron]

Just a thought: maybe it makes sense to convert the other with_ (not without) function to return Result too. Just to prevent future breaking changes on those.

[milux]

Just a thought: maybe it makes sense to convert the other with_ (not without) function to return Result too. Just to prevent future breaking changes on those.

Good thought, also thought that. Didn't realize that there was only one function left, though. 😆
Bumped to 0.6.0-rc.1 accordingly, because API breaking change.

[milux]

@ctron Also tried to clean up and streamline dependencies. Maybe you want to review that additional changes before merge?

[milux]

@ctron One more question: Did you intentionally exclude Cargo.lock from the repo? My last commit includes it because AFAIK that harms reproducibility across developer teams.

[ctron]

@ctron One more question: Did you intentionally exclude Cargo.lock from the repo? My last commit includes it because AFAIK that harms reproducibility across developer teams.

As this is a library, the lock file is not committed as that used to be the default. I wouldn't want to change it just for this project, and as part of this PR.

[milux]

@ctron One more question: Did you intentionally exclude Cargo.lock from the repo? My last commit includes it because AFAIK that harms reproducibility across developer teams.

As this is a library, the lock file is not committed as that used to be the default. I wouldn't want to change it just for this project, and as part of this PR.

Good point, will undo...

[milux]

@ctron Is the current state acceptable and can we progress to merge?

[milux]

It would also be very helpful for https://github.com/csaf-rs/csaf to have this released as 0.6.0-rc.1 in order to include this patch there, as there are failing tests, see oasis-tcs/csaf#1057.

[helio-frota]

@milux hi ctron is on pto

I have no gh permission to merge yet 👍

[ctron]

@milux sorry, I was on vacation and did not update my GH busy status to make this clear.

[milux]

@ctron Could you please do a 0.6.0-rc.1 release?

[ctron]

Done!