Skip to content

docs(desktop): add v0.1.8 release evidence and QA sheet#103

Merged
Prekzursil merged 1 commit intomainfrom
docs/desktop-v0.1.8-evidence-2026-03-03
Mar 3, 2026
Merged

docs(desktop): add v0.1.8 release evidence and QA sheet#103
Prekzursil merged 1 commit intomainfrom
docs/desktop-v0.1.8-evidence-2026-03-03

Conversation

@Prekzursil
Copy link
Owner

@Prekzursil Prekzursil commented Mar 3, 2026

Summary

  • add 2026-03-03-desktop-v0.1.8-release-evidence.md with Desktop Release run/result and Windows artifact links
  • add 2026-03-03-windows-desktop-polish-findings.md as the structured extended QA capture sheet
  • document prerelease/latest-manifest behavior for desktop-v0.1.8

Verification

  • gh run view 22602528982 (Desktop Release success)
  • gh release view desktop-v0.1.8 (Windows EXE/MSI present, prerelease=true)
  • python3 scripts/verify_desktop_updater_release.py (latest manifest currently resolves to 0.1.7 as expected for prerelease state)

Capture workflow/release artifact evidence for desktop-v0.1.8 and add a structured Windows QA findings template for extended shorts/captions evaluation.

Co-authored-by: Codex <noreply@openai.com>
@devloai
Copy link

devloai bot commented Mar 3, 2026

Unable to trigger custom agent "Code Reviewer". You have run out of credits 😔
Please upgrade your plan or buy additional credits from the subscription page.

@chatgpt-codex-connector
Copy link

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@qodo-code-review
Copy link

Review Summary by Qodo

Add v0.1.8 release evidence and Windows QA findings template

📝 Documentation

Grey Divider

Walkthroughs

Description
• Add v0.1.8 release evidence document with workflow and artifact links
• Create Windows QA findings template for structured testing capture
• Document prerelease behavior and updater manifest verification
Diagram
flowchart LR
  A["Release v0.1.8"] --> B["Evidence Document"]
  A --> C["Windows Artifacts"]
  B --> D["Workflow Links"]
  B --> E["Updater Verification"]
  C --> F["EXE/MSI URLs"]
  A --> G["QA Template"]
  G --> H["Test Findings"]
  G --> I["Defect Triage"]
Loading

Grey Divider

File Changes

1. docs/plans/2026-03-03-desktop-v0.1.8-release-evidence.md 📝 Documentation +44/-0

Release evidence and workflow verification documentation

• Documents release metadata including tag, URL, and publication timestamp
• Records Desktop Release workflow run details with per-platform job links
• Lists Windows installer artifact URLs (EXE and MSI)
• Explains prerelease behavior and updater manifest resolution to v0.1.7

docs/plans/2026-03-03-desktop-v0.1.8-release-evidence.md


2. docs/plans/2026-03-03-windows-desktop-polish-findings.md 📝 Documentation +51/-0

Windows QA findings and testing template

• Provides structured template for Windows QA testing of v0.1.8
• Captures environment configuration and installation method details
• Documents functional scenario outputs including captions, translation, and shorts jobs
• Includes subjective quality assessment and defect triage sections

docs/plans/2026-03-03-windows-desktop-polish-findings.md


Grey Divider

Qodo Logo

@coderabbitai
Copy link

coderabbitai bot commented Mar 3, 2026

Warning

Rate limit exceeded

@Prekzursil has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 37 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e8d818a and f13792b.

📒 Files selected for processing (2)
  • docs/plans/2026-03-03-desktop-v0.1.8-release-evidence.md
  • docs/plans/2026-03-03-windows-desktop-polish-findings.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs/desktop-v0.1.8-evidence-2026-03-03

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@qodo-code-review
Copy link

qodo-code-review bot commented Mar 3, 2026

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider


Remediation recommended

1. Updater verify needs repo root 🐞 Bug ✓ Correctness
Description
The release evidence doc instructs running python3 scripts/verify_desktop_updater_release.py but
doesn’t state it must be executed from the repository root (or passed --config). Because the
script’s default config path is relative, running it from another working directory (common when
reading the doc in docs/plans/) will fail with FileNotFoundError and block verification
reproduction.
Code

docs/plans/2026-03-03-desktop-v0.1.8-release-evidence.md[R25-30]

+## Updater manifest verification
+Command:
+
+```bash
+python3 scripts/verify_desktop_updater_release.py
+```
Evidence
The doc provides a relative command with no working-directory context, while the verifier script
uses a relative default config path and explicitly errors if it can’t find that file from the
current working directory.

docs/plans/2026-03-03-desktop-v0.1.8-release-evidence.md[25-30]
scripts/verify_desktop_updater_release.py[14-15]
scripts/verify_desktop_updater_release.py[54-59]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The documentation command for verifying the desktop updater manifest relies on relative paths and will fail if executed from a non-repo-root working directory.

## Issue Context
`scripts/verify_desktop_updater_release.py` defaults to `apps/desktop/src-tauri/tauri.conf.json` via a relative `Path(...)` and raises `FileNotFoundError` if it cannot find it.

## Fix Focus Areas
- docs/plans/2026-03-03-desktop-v0.1.8-release-evidence.md[25-30]
- scripts/verify_desktop_updater_release.py[14-59]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Advisory comments

2. Empty checkbox placeholders 🐞 Bug ✧ Quality
Description
The Windows QA sheet includes task-list items with no text (- [ ]). This is inconsistent with
existing repo checklists and makes the template harder to use/search (no label for what each
checkbox represents).
Code

docs/plans/2026-03-03-windows-desktop-polish-findings.md[R40-48]

+## Triage
+### Blocking defects
+- [ ]
+
+### Medium UX issues
+- [ ]
+
+### Polish improvements
+- [ ]
Evidence
The new QA sheet contains blank checkbox lines, while existing repository checklists consistently
include descriptive text after the checkbox.

docs/plans/2026-03-03-windows-desktop-polish-findings.md[40-48]
docs/GOVERNANCE.md[288-298]
docs/BRANCH_PROTECTION.md[174-199]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The QA template uses empty task-list items (`- [ ]`) which reduces clarity and is inconsistent with other repo checklists.

## Issue Context
Other docs in the repo use `- [ ] &lt;description&gt;` consistently.

## Fix Focus Areas
- docs/plans/2026-03-03-windows-desktop-polish-findings.md[40-48]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 3, 2026

@Prekzursil Prekzursil merged commit 8c7f5f1 into main Mar 3, 2026
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant