fix: Fix Windows credential storage via windows-native keyring feature

[23prime]

Checklist

• Target branch is main
• Status checks are passing

Summary

Fix credential storage on Windows by adding the windows-native feature to the keyring crate, which enables Windows Credential Manager as the backend.

Reason for change

After the v0.1.3 release, real-device testing on Windows revealed that bl auth login completed without error but credentials were not actually stored — causing bl auth status to fail with "API key not found". The root cause was that the async-secret-service feature (Linux D-Bus) was the only backend enabled; without windows-native, the keyring crate had no working backend on Windows and silently returned Ok(()) instead of storing anything.

Changes

• Cargo.toml: Add windows-native keyring feature as a Windows-only platform dependency ([target.'cfg(windows)'.dependencies]) to avoid expanding the dependency graph on Linux/macOS
• .github/workflows/check-rust.yml: Add check-windows job on windows-latest to catch platform-specific compilation issues early

Notes

Cargo.lock records dependencies for all target platforms regardless of the build host, so the single lock file works correctly for both Linux CI and Windows CI with --locked.

[coderabbitai]

📝 Walkthrough

Walkthrough

The keyring crate dependency in Cargo.toml now enables the "windows-native" feature alongside existing features. This is a single-line dependency configuration update affecting platform-specific functionality.

Changes

Cohort / File(s)	Summary
Dependency Configuration Cargo.toml	Added "windows-native" feature flag to the keyring crate dependency.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A whisker twitch, a feature bright,
Windows-native, what a sight!
Keyring dancing with new flair,
Platform magic in the air! 🔑✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately describes the main change: adding the windows-native keyring feature to fix Windows credential storage, which is the core objective of the PR.
Description check	✅ Passed	The PR description clearly explains the purpose (fixing credential storage on Windows), the root cause, and the specific changes made to address the issue.

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

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/windows-keyring

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch fix/windows-keyring

---

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

[Copilot]

Pull request overview

This PR updates the Rust dependency configuration so the CLI can use the Windows Credential Manager backend via keyring when running on Windows, avoiding cases where bl auth login does not persist the API key.

Changes:

• Enable the keyring crate’s windows-native feature in Cargo.toml.
• Regenerate Cargo.lock to include the newly-resolved transitive dependencies (e.g., windows-sys, byteorder).

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.

File	Description
Cargo.toml	Enables keyring’s Windows backend feature to support Credential Manager.
Cargo.lock	Updates lockfile to reflect the dependency graph after enabling windows-native.