chore(release): bump desktop to 2026.7.4

[Astro-Han]

Summary

Bump the PawWork desktop release version from 2026.7.3 to 2026.7.4 in the package manifest and Bun lockfile. This requested stable release preparation has no related issue.

Why

The next July stable release needs a unique CalVer version before macOS and Windows artifacts can be built, notarized, published, and mirrored from one pinned commit.

Related Issue

None; this is the requested v2026.7.4 stable release bump.

Human Review Status

Approved by @Astro-Han

Review Focus

Confirm the diff changes only the desktop package version and its lockfile workspace entry to 2026.7.4.

Risk Notes

The visible UI check is not applicable because this changes no UI or copy. The version is the source for release asset names and updater metadata, so all three final release targets must build the merged commit.

How To Verify

Version contract: RED on 2026.7.3, GREEN on 2026.7.4
Release contract tests: 77 passed, 0 failed
Release typecheck: passed (tsgo -p tsconfig.release.json)
Frozen install: passed with no lockfile changes
Root and site audits: zero high or critical findings
Diff check: no whitespace errors

Screenshots or Recordings

Not applicable; no visible UI changes.

Checklist

How to use this checklist:

• Tick a box by replacing [ ] with [x]. Do not edit, add, or remove items.
• The bot-applied label items can only be honestly ticked AFTER the PR is opened and the labeler / priority-triage bots have run — return to the PR description and tick them then.
• Most items are required. The few that are conditional are explicitly marked (conditional); for those, leave unticked if they truly do not apply and explain why in Risk Notes. All other items must be ticked before requesting human review.

• Type label — this PR carries exactly one of bug, enhancement, task, documentation. Type labels are author-added; the labeler bot does NOT assign them. Add the label in the GitHub UI, then tick this.
• Routing labels — this PR carries at least one of app, ui, platform, harness, ci. The labeler bot assigns these on PR open based on changed paths. Confirm the bot's choice (or override if wrong), then tick this.
• Priority label — this PR carries exactly one of P0, P1, P2, P3. The priority-triage bot suggests one on PR open. Confirm or override, then tick this.
• Human Review Status above is set to Pending, Approved by @<reviewer>, or Not required: <reason> (default is Pending; "not required" is restricted to bot-authored low-risk PRs).
• I linked the related issue, or stated in Summary why there is no issue.
• I described the review focus and any meaningful risks.
• I replaced the example block in How To Verify with the real verification steps and the key result for each.
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope.
• (conditional) I manually checked visible UI or copy changes when needed, with screenshots or recordings. Leave unticked only if no visible UI or copy changed.
• (conditional) I considered macOS and Windows impact for platform, packaging, updater, signing, paths, shell, or permissions changes. Leave unticked only if no platform/packaging surface was touched.
• (conditional) I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant. Leave unticked only if none of those surfaces was touched.
• I reviewed the final diff for unrelated changes and suspicious dependency changes.
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English.

[github-actions]

Suggested priority: P2 (includes non-doc, non-test paths outside the low-risk bucket).

P1/P0 are reserved for maintainer confirmation. Please relabel manually if this is a release blocker, security issue, data-loss risk, or updater/runtime failure.

[coderabbitai]

📝 Walkthrough

Walkthrough

The desktop Electron package version is bumped from 2026.7.3 to 2026.7.4 in its package manifest.

Changes

Desktop release metadata

Layer / File(s)	Summary
Update desktop package version packages/desktop-electron/package.json	The package version is incremented from 2026.7.3 to 2026.7.4.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• Astro-Han/pawwork#1520: Bumps the same desktop package version field.
• Astro-Han/pawwork#1527: Uses the same desktop package version-bump pattern.
• Astro-Han/pawwork#1477: Updates the same desktop release manifest version.

Suggested labels: desktop

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
Title check	✅ Passed	The title clearly states the release bump to desktop version 2026.7.4.
Description check	✅ Passed	The description matches the template and fills the required sections with concrete details.

✨ 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 chore/release-2026.7.4

---

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