Severity field is being ignored when computing content ID for AdvisoryV2

[keshav-space]

vulnerablecode/vulnerabilities/utils.py

Lines 678 to 692 in 2ff2906

	normalized_data = {
	"aliases": normalize_list(advisory_data.aliases),
	"summary": normalize_text(advisory_data.summary),
	"impacted_packages": sorted(
	[impact.to_dict() for impact in advisory_data.impacted_packages.all()],
	key=lambda x: json.dumps(x, sort_keys=True),
	),
	"patches": sorted(
	[patch.to_patch_data().to_dict() for patch in advisory_data.patches.all()],
	key=lambda x: json.dumps(x, sort_keys=True),
	),
	"references": [ref for ref in normalize_list(advisory_data.references) if ref],
	"weaknesses": normalize_list(advisory_data.weaknesses),
	}
	normalized_data["url"] = advisory_data.url

[Mahaboobunnisa123]

Hi @keshav-space, I’m interested in working on this bug. could you please assign this issue to me?
I will update the AdvisoryV2 content-id computation to include a normalized severity field so that changes in severity produce a different content ID, add a regression test that currently fails (severity change shouldn’t keep the same content ID), and open a PR with the fix. If you prefer, I can also include a small migration/management step to recompute content IDs for existing AdvisoryV2 rows or do that as a follow-up PR. let me know if my approach is acceptable. Thanks!