Rename Feedser to Concelier
This commit is contained in:
		| @@ -2,11 +2,11 @@ | ||||
|  | ||||
| This guide complements the Sprint 1–2 normalized versions rollout. It documents recommended indexes and aggregation patterns for querying `AffectedPackage.normalizedVersions`. | ||||
|  | ||||
| For a field-by-field look at how normalized rules persist in MongoDB (including provenance metadata), see Section 8 of the [Feedser SemVer Merge Playbook](merge_semver_playbook.md). | ||||
| For a field-by-field look at how normalized rules persist in MongoDB (including provenance metadata), see Section 8 of the [Concelier SemVer Merge Playbook](merge_semver_playbook.md). | ||||
|  | ||||
| ## 1. Recommended indexes | ||||
|  | ||||
| When `feedser.storage.enableSemVerStyle` is enabled, advisories expose a flattened | ||||
| When `concelier.storage.enableSemVerStyle` is enabled, advisories expose a flattened | ||||
| `normalizedVersions` array at the document root. Create these indexes in `mongosh` | ||||
| after the migration completes (adjust collection name if you use a prefix): | ||||
|  | ||||
| @@ -105,4 +105,4 @@ Use this to confirm the merge dedupe logic keeps only one normalized rule per un | ||||
| - [ ] Notify downstream services that consume advisory snapshots about the new `normalizedVersions` array. | ||||
| - [ ] Update export fixtures once dedupe verification passes. | ||||
|  | ||||
| Additional background and mapper examples live in [Feedser SemVer Merge Playbook](merge_semver_playbook.md). | ||||
| Additional background and mapper examples live in [Concelier SemVer Merge Playbook](merge_semver_playbook.md). | ||||
|   | ||||
		Reference in New Issue
	
	Block a user