chore(component):SP-3975 Bypass version resolution logic when the req…

[agustingroh]

…uirement already contains a fixed version in GetComponent method

Summary by CodeRabbit

Release Notes

• Performance Improvements

  • Optimized component version resolution to bypass unnecessary lookups when fixed versions are specified across all supported package managers.

• Documentation

  • Added comprehensive changelog documenting project history and version updates.

• Chores

  • Updated project dependencies to improve compatibility and codebase maintenance.
  • Removed obsolete IDE-specific configuration files.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR removes IntelliJ IDE configuration, introduces a CHANGELOG documenting v0.3.0 release notes, adjusts Go module dependencies, and optimizes GetComponent to bypass version resolution when handling fixed-version requirements without range operators.

Changes

Cohort / File(s)	Summary
IDE Configuration Removal .idea/sqldialects.xml	Deleted project-specific SQL dialect mappings for test files; no functional impact.
Documentation CHANGELOG.md	New changelog file added following Keep a Changelog format, documenting v0.3.0 release (2026-01-29) with GetComponent optimization notes.
Dependency Management go.mod	Adjusted indirect and direct dependencies: removed pkggodev-client, packageurl-go (initially), sanitize/chardet, robotstxt, appengine; added google/go-cmp, packageurl-go (re-added), testify, otel components, zap.
Core Logic Enhancement pkg/services/component.go	Added early-return optimization in GetComponent: when requirement is a fixed version (no range operators: <>={^~*|[]()), method returns directly with provided PURL and version, bypassing database lookup. Covers npm, pip, maven/nuget, cargo, composer, gems ecosystems.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 A version so fixed, no ranges to find,
We skip the lookup, leaving slow queries behind!
Changelogs written, dependencies aligned—
A release well-crafted, with optimization in mind! 📝✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(component):SP-3975 Bypass version resolution logic when the req…' is directly related to the main change in the pull request—introducing an early return in GetComponent to bypass version resolution for fixed versions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Around line 10-15: The changelog entry for version 0.3.0 currently uses a
future release date (2026-01-29); update the CHANGELOG.md entry so the date is
not in the future by either moving the "## [0.3.0] - 2026-01-29" block under an
"Unreleased" heading (if the release isn’t cut yet) or replacing the date with
the actual release/tag date when you create the tag; ensure the paragraph
describing GetComponent and the bullet points remain intact and only the version
header is adjusted.

In `@pkg/services/component.go`:
- Around line 67-74: The current early-return treats purlReq as a fixed version
without checking hyphen ranges; update the condition around purlReq (the block
that returns types.ComponentResponse with Version: purlReq) to also detect and
exclude hyphen ranges (e.g. "1.2.3 - 2.0.0") so they are not treated as fixed
versions—implement this by adding a hyphen-range check (for example a regexp
like `\S+\s*-\s*\S+` or testing for " - " with optional surrounding whitespace)
against purlReq and only return the fixed-version response when purlReq does not
match that hyphen-range pattern.