What's Changed

• Support new bearer auth scheme and offset+limit pagination (#69)

What's Changed

New

• Added run-level log upload support for automation result uploads.

Pull Requests

• #68 Add create run logs

Full Changelog: v0.8.0...v0.8.1

What's Changed

New

• Added interactive qasphere auth commands (login, logout, status) for browser-based authentication via OAuth 2.0 Device Authorization Grant (RFC 8628), removing the need to manually manage API keys.
• Credentials are now persisted in the OS keyring when available, with a permission-restricted (0600) file fallback at ~/.config/qasphere/credentials.json.
• auth status displays the resolved credential source and the authenticated user details.

Improved

• README rewritten to highlight public API commands and agentic workflows, with workflow examples moved above installation.

Pull Requests

• #64 Add interactive login
• #66 Improve README.md

Full Changelog: v0.7.0...v0.8.0

What's Changed

New

• Added the new qasphere api command for direct access to the QA Sphere public API, including resource subcommands for projects, runs, test cases, results, folders, files, users, and more.

Improved

• Fixed incorrect Playwright upload mapping by enforcing exact marker matching, supporting fan-out for multiple test case annotations, deduplicating shared attachments, and making upload summaries report results vs target test cases clearly.
• Made parsed marker metadata the source of truth during upload mapping, and moved duplicate-target validation ahead of run creation and --create-tcases side effects.

Pull Requests

• #58 Add public API commands
• #61 Fix incorrect Playwright upload mapping to QA Sphere runs
• #63 [codex] Fix marker resolution and duplicate mapping validation

Full Changelog: v0.6.0...v0.7.0

What's Changed

• Handle API rate limiting by @hi-rai in #57
• Add support for uploading run level failure logs by @hi-rai in #56
• Support allure run level failure logs by @hi-rai in #59

Full Changelog: v0.5.0...v0.6.0

Contributors

• @hi-rai

Adds allure-upload support to QAS CLI.

• Upload Allure 2 results directories to QA Sphere
• Match test cases via TMS links or test name markers
• Upload attachments, including nested step attachments
• Support --force to skip invalid result files and continue

Also includes updated CLI help and README docs for Allure usage.

Full Changelog: v0.4.6...v0.5.0

New Features

• CamelCase and snake_case marker matching for JUnit XML — Test case markers like TestPrj002CartItems or test_PRJ_002_cart_items are now recognized in JUnit reports, supporting
  Go and Java test naming conventions (#51)
• Bare <testsuite> root element support — junit-upload now accepts JUnit XML files with <testsuite> as the root element (common in Maven Surefire, TestNG, and JUnit 4/5 per-class reports), removing the need to pre-merge files with tools like junit-merge (#53)

Bug Fixes

• JUnit XML with attribute-less elements no longer fails — <testsuites> and <testsuite> elements without XML attributes (e.g. output from junit-merge) are now parsed correctly
  (#52)

Internal

• Marker detection/extraction consolidated into a new MarkerParser class, replacing scattered regex logic

Full Changelog: v0.4.5...v0.4.6

What's Changed

New Features

• Add support for creating test cases (#39)
• Add time tracking information to uploaded results (#41)

Other

• Minor README update (#43)
• Add Claude Code integration with author-association guard (#45)

Full Changelog: v0.4.4...v0.4.5