Swift relies on Version, not hash

[Ryan Brandenburg (ryanbrandenburg)]

After chatting with some team-members we decided that Version was the more useful identifier after all. This PR makes version the ComponentBaseId identifier and removes the constructors which weren't really achieving anything anyway.

Most of the test changes relate to either the expected ID changing or the lack of constructor enforcement for some parameters.

[Copilot]

Copilot review overview

🟡 Changes recommended

The detector version was not incremented, and removing a public constructor breaks existing Contracts consumers.

Review effort: Balanced
Findings: 1 · 1 · 2

Open (4)

• Removing public constructor breaks source and binary compatibility · New
• Increment detector version for changed component IDs · New
• Rename test to reflect object initializer behavior · New
• Rename test to reflect no components being registered · New

What changed in this PR

Updates Swift component identity to rely on repository URL and package version rather than commit hash.

Changes:

• Uses version in Swift component IDs.
• Skips packages without versions while allowing missing revisions.
• Replaces constructor usage with object initializers and updates tests.

File	Description
src/​Microsoft.ComponentDetection.Contracts/​TypedComponent/​SwiftComponent.cs	Changes identity and removes constructors.
src/​Microsoft.ComponentDetection.Detectors/​swiftpm/​SwiftResolvedComponentDetector.cs	Requires versions during detection.
test/​Microsoft.ComponentDetection.Contracts.Tests/​TypedComponentSerializationTests.cs	Updates Swift serialization setup.
test/​Microsoft.ComponentDetection.Detectors.Tests/​SwiftComponentTests.cs	Updates identity and initialization tests.
test/​Microsoft.ComponentDetection.Detectors.Tests/​SwiftResolvedDetectorTests.cs	Updates detector expectations.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:

• The detector detects more or fewer components than before
• The detector generates different parent/child graph relationships than before
• The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂

[Copilot]

Copilot review overview

🟢 Approval recommended

The implementation and tests consistently apply the intended version-based Swift identity behavior.

Review effort: Balanced
Findings: None

Resolved since last review (4)

• Removing public constructor breaks source and binary compatibility
• Increment detector version for changed component IDs
• Rename test to reflect no components being registered
• Rename test to reflect object initializer behavior

[Ryan Brandenburg (ryanbrandenburg)]

The change in detections count is expected, the "revision+branch" sample is no longer valid.