ci: change ci workflow

[watermarkhu]

Summary by CodeRabbit

• Chores
  • Updated CI/CD pipeline to test across multiple dependency resolution strategies
  • Replaced release management tooling and process
  • Reset package version to 0.0.0

[coderabbitai]

Warning

Rate limit exceeded

@watermarkhu has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 7 minutes and 16 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 55773065-363f-4140-a735-96565887f5c0

📥 Commits

Reviewing files that changed from the base of the PR and between 3d55367 and 013ea83.

📒 Files selected for processing (3)

• .github/renovate.json5
• .github/workflows/qualify.yaml
• pyproject.toml

📝 Walkthrough

Walkthrough

The pull request updates CI/CD workflows and project configuration. The test matrix in qualify.yaml is expanded with a resolution dimension for dependency resolution modes. The release.yaml workflow is significantly refactored to use RonaldPhilipsen/semVersie for versioning, with updated deployment steps including direct git operations and release creation. The project version is reset to 0.0.0 with semantic-release configuration removed.

Changes

Cohort / File(s)	Summary
CI/CD Workflows .github/workflows/qualify.yaml, .github/workflows/release.yaml	Test matrix extended with resolution dimension; environment variables added for Python version and UV resolution. Release workflow rewritten to use semVersie tool; deploy job now performs direct git operations, version bumping, tag creation, package publishing, and release creation via gh CLI instead of semantic-release and action-gh-release.
Project Configuration pyproject.toml	Package version reset to 0.0.0; entire [tool.semantic_release] configuration block removed.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Poem

🐰 With whiskers twitched and nose held high,
We've swapped our versioning in the sky,
New workflows dance, resolutions blend,
From semVersie—a trusted friend!
The tags will fly, the releases soar,
Our CI/CD changed to the core. ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is vague and overly generic, using only 'change ci workflow' without describing what specific CI changes are being made or their purpose.	Make the title more specific by describing the main change, such as 'ci: update test matrix with resolution dimension' or 'ci: migrate from semantic-release to semVersie' to clearly communicate the primary objective.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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 unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci-update

---

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.}

[github-actions]

Test Results

10 files + 5 10 suites +5 1m 4s ⏱️ +31s
116 tests ± 0 116 ✅ ± 0 0 💤 ±0 0 ❌ ±0 
1 160 runs +580 1 160 ✅ +580 0 💤 ±0 0 ❌ ±0 

Results for commit 013ea83. ± Comparison against base commit 565b88d.

♻️ This comment has been updated with latest results.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.30%. Comparing base (565b88d) to head (013ea83).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@ Coverage Diff @@## main #61 +/- ##
=======================================
Coverage 95.30% 95.30% =======================================
Files 5 5 Lines 490 490 Branches 84 84 =======================================
Hits 467 467 Misses 9 9 Partials 14 14 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/qualify.yaml:
- Line 68: The artifact upload name conflicts between parallel matrix legs
because the workflow uses a fixed name "python${{ matrix.python-version }}" for
actions/upload-artifact@v7; update the artifact name to include the resolution
matrix axis so each leg is unique (for example incorporate "${{
matrix.resolution }}" into the artifact name) by changing the upload step that
references python${{ matrix.python-version }} to use both matrix.python-version
and matrix.resolution (e.g., python${{ matrix.python-version }}-${{
matrix.resolution }}).
In @.github/workflows/release.yaml:
- Around line 4-10: The workflow currently triggers privileged operations
(add-pr-label: true and steps that use the private key / app token for publish)
on pull_request, which blocks external/fork PRs; split the workflow so that
non-privileged tasks (e.g., version calculation) remain under pull_request, and
move privileged steps — the publish step and app-token/private-key usage (the
steps using the private key and app token generation and any step with
add-pr-label: true) — into a separate job or workflow triggered only by a
trusted event such as push to main or workflow_run; update triggers so
pull_request remains for read-only analysis, and create a push/workflow_run
entry (or a dependent workflow) that runs the publish/app-token jobs with access
to secrets.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f1032c3f-6a6e-4dfa-9384-81b519f61ae2

📥 Commits

Reviewing files that changed from the base of the PR and between 565b88d and 3d55367.

📒 Files selected for processing (3)

• .github/workflows/qualify.yaml
• .github/workflows/release.yaml
• pyproject.toml