Hub 0.8.43

[pbrassel]

Summary by CodeRabbit

• Bug Fixes

  • Improved error response handling to correctly parse API responses using alternative field names.

• Documentation

  • Updated API types reference documentation.
  • Refreshed code coverage metrics.

• Tests

  • Enhanced test fixtures and infrastructure for improved reliability.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR upgrades the Hub Python client to version 0.8.43, updating the test environment configuration, relaxing API response parsing to accept alternative field names, documenting new API types, and adapting the test suite to use consistent lowercase values and simplified assertions reflecting improved API behavior.

Changes

Hub Version 0.8.43 Upgrade

Layer / File(s)	Summary
Environment and Version Update .env.test, README.md	PYTEST_HUB_VERSION updated from 0.8.37 to 0.8.43; code coverage badge adjusted to 95%.
API Response Contract Enhancement flame_hub/_exceptions.py	ErrorResponse.status_code now validates against both "statusCode" and "status" API response keys via Pydantic AliasChoices.
API Types Documentation Update docs/types_api.rst	Deprecated types (UNSET_T, FilterParams, analysis status types) removed from API docs; new process/logging types (ProcessStatus, LogLevel, LogChannel) documented.
Auth Test Fixtures and Cleanup tests/test_auth.py	Auth fixtures and update tests converted to lowercase random strings; xfail decorators removed from test_get_robot and test_get_client.
Core Test Simplification tests/test_core.py	analysis_code_bucket fixture refactored to query existing CODE buckets instead of creating resources; test_build_analysis simplified to direct API re-fetch and assertion.

Possibly related PRs

• PrivateAIM/hub-python-client#102: Related updates to Hub versioning and process status handling reflecting API evolution in types and test expectations.
• PrivateAIM/hub-python-client#107: Related update to .env.test PYTEST_HUB_VERSION configuration for Hub version alignment.

Poem

🐰 A version hop from .37 to .43, the Hub says,
Now status codes wear two names, we accept either way,
ProcessStatus and LogLevel shine in the docs' light,
Tests lowercase their strings and xfails take flight,
Buckets query instead of create, simpler and bright!

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title 'Hub 0.8.43' refers to a version bump but doesn't clearly describe the primary changes, which include dependency updates, documentation changes, test improvements, and error handling enhancements.	Consider a more descriptive title that highlights the main changes, such as 'Update Hub to 0.8.43 with documentation and test improvements' or simply 'Bump Hub version to 0.8.43 and update dependencies'.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch hub-0.8.43

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 1: Code coverage fell from 96% to 95% after this PR; add tests exercising
the newly-introduced functionality to restore coverage, run the project's
coverage tool locally to confirm, and only update the README badge (the image
line in README.md) if the reported coverage is legitimately changed. Identify
the new or modified modules/files introduced by this PR, write unit/integration
tests that cover their edge cases and error paths, run the repository's
test/coverage command to verify coverage returns to the required threshold, and
update the README badge if the verified coverage number differs from the current
badge.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f92550e7-f56b-40c2-a287-2137c5a3d7cc

📥 Commits

Reviewing files that changed from the base of the PR and between 1a13179 and cb15d2d.

⛔ Files ignored due to path filters (1)

• poetry.lock is excluded by !**/*.lock

📒 Files selected for processing (6)

• .env.test
• README.md
• docs/types_api.rst
• flame_hub/_exceptions.py
• tests/test_auth.py
• tests/test_core.py

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Code coverage decreased from 96% to 95%.

Consider verifying that the new code introduced in this PR is adequately tested. A coverage drop may indicate untested functionality or edge cases.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 1, Code coverage fell from 96% to 95% after this PR; add
tests exercising the newly-introduced functionality to restore coverage, run the
project's coverage tool locally to confirm, and only update the README badge
(the image line in README.md) if the reported coverage is legitimately changed.
Identify the new or modified modules/files introduced by this PR, write
unit/integration tests that cover their edge cases and error paths, run the
repository's test/coverage command to verify coverage returns to the required
threshold, and update the README badge if the verified coverage number differs
from the current badge.