GitHub releases are behind distributed versions - missing v1.11.x and v1.12.x tags

## Issue Summary

The GitHub releases are significantly behind the versions being distributed. Currently:

- **Latest GitHub release**: `v1.10.1`
- **Current distributed version**: `v1.12.1` (via `q --version`)

## Impact

This creates confusion for users and the open source community who rely on GitHub releases to:
- Track version history and changes
- Understand what features/fixes are available
- Follow the project's development progress
- Integrate with automated tooling that monitors releases

## Evidence

Recent merged PRs show active development (May 2025):
- SSO client improvements (#1929)
- Token refresh fixes (#1920)
- MCP loading status enhancements (#1919)
- Multiple dependency updates

However, no corresponding GitHub releases have been created for versions 1.11.x or 1.12.x.

## Suggested Solution

Could the team please:
1. Create GitHub releases for missing versions (v1.11.x, v1.12.x)
2. Include release notes documenting changes
3. Establish a process to ensure future releases are tagged consistently

## Community Value

Proper release tagging helps maintain transparency and allows the community to better engage with the project's evolution. Many users depend on GitHub releases for version tracking and integration workflows.

Thanks for considering this improvement! Happy to help with any additional context needed.

---
*Discovered while comparing repository activity with local installation version*

Beginne damit, die GitHub-Releases mit der von `q --version` gemeldeten verteilten Version zu vergleichen, und prüfe anschließend die im Issue aufgeführten gemergten PRs auf Änderungen in v1.11.x und v1.12.x. Erledigt ist die Aufgabe, wenn die fehlenden GitHub-Releases mit Release Notes vorhanden sind und ein dokumentierter Ansatz dafür besteht, zukünftige Tags konsistent zu halten.

Vom Indexierungsmodell aus dem Issue-Text verfasst.