Update to 1.8.2 in pyproject.toml

[bouwew]

Summary by CodeRabbit

• Chores
  • Version updated to 1.8.2 (stable release).

[coderabbitai]

Walkthrough

The project version in pyproject.toml is bumped from the alpha pre-release version "1.8.2a0" to the stable release version "1.8.2", marking the transition from alpha development to a production-ready release.

Changes

Cohort / File(s)	Summary
Version Release Update pyproject.toml	Updated project version in [project] section from "1.8.2a0" to "1.8.2"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• plugwise/python-plugwise#635 — Identical version bump change in a similar project, transitioning from alpha pre-release to stable release

Poem

🐰 The alpha phase now rests at bay,
Version one-point-eight-point-two's here to stay!
No longer marked with "a," so free,
A stable release for all to see! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Update to 1.8.2 in pyproject.toml" is fully related to the main change in the changeset. The title accurately reflects the primary modification: updating the project version from "1.8.2a0" to "1.8.2" in pyproject.toml. The title is concise, clear, and specific, providing sufficient information for a teammate scanning the git history to understand that this is a version bump. The phrasing is direct without unnecessary noise or vague terminology.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-1.8.2

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eddea45 and bacfb0f.

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Ruff check and force

🔇 Additional comments (1)

pyproject.toml (1)

7-7: Version bump correctly isolated—no additional updates needed.

The change from "1.8.2a0" to "1.8.2" is properly formatted and valid. Verification confirms the package version is managed solely through pyproject.toml with no hardcoded __version__ constants, changelog file, or CI workflows requiring synchronization. The test data references (e.g., smile_version parameters) are device firmware versions, not package versions, so they are unaffected.

This change is complete as-is and ready for merge.

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (eddea45) to head (bacfb0f).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #805   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines         3403      3403           
=========================================
  Hits          3403      3403           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.