Bump version to 3.0.0-alpha.69

[atterpac]

Summary by CodeRabbit

• Chores
  • Bumped internal desktop runtime package to version 3.0.0-alpha.69.
  • No changes to features, settings, or behavior; this is a routine dependency update.
  • Build and installation processes remain unchanged.
  • No user-facing UI or API adjustments included.
  • Existing projects continue to work as before with identical functionality and performance.
  • No action required from users.

[coderabbitai]

Walkthrough

Bumps the version in v3/internal/runtime/desktop/@wailsio/runtime/package.json from 3.0.0-alpha.68 to 3.0.0-alpha.69. No other fields changed.

Changes

Cohort / File(s)	Summary of Changes
Version bump v3/internal/runtime/desktop/@wailsio/runtime/package.json	Updated "version": 3.0.0-alpha.68 → 3.0.0-alpha.69

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• @wailsio version bump #3966 — Similar version bump in the same package.json file.
• [V3 Runtime] Ensure JS package has parity with various node versions #3821 — Earlier version bump and field adjustments in the same package.json.

Suggested reviewers

• leaanthony

Pre-merge checks (2 passed, 1 warning)

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The current PR description is empty and lacks all required sections from the repository template, including the change summary, issue reference, change type, testing details, and checklist.	Please fill out the PR description per the template by adding a detailed summary, issue linkage, selecting the type of change, describing test steps with wails doctor output, and completing the checklist.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title precisely reflects the primary change—bumping the version to 3.0.0-alpha.69—and is concise and clear.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

A tiny hop, a version twirls,
From alpha dot sixty-eight it swirls—
To sixty-nine, the carrots shine,
My paws tap semvers, right on time.
Changelog breeze, no files to maze,
Just bump and thump—release-day haze! 🥕🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
		  - name: "Undocumented Breaking Changes"
			  mode: "warning"
			  instructions: |
				  Flag potential breaking changes that are not documented:
				  1. Identify changes to public APIs/exports, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints (including removed/renamed items and changes to types, required params, return values, defaults, or behavior).
				  2. Ignore purely internal/private changes (e.g., code not exported from package entry points or marked internal).
				  3. Verify documentation exists: a "Breaking Change" section in the PR description and updates to CHANGELOG.md.

Please share your feedback with us on this Discord post.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9d51280 and 37905b6.

📒 Files selected for processing (1)

• v3/internal/runtime/desktop/@wailsio/runtime/package.json (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-01-15T22:33:30.639Z

Learnt from: fbbdev
PR: wailsapp/wails#4001
File: v3/internal/generator/testdata/output/lang=TS/UseInterfaces=true/UseNames=false/github.com/wailsapp/wails/v3/internal/generator/testcases/function_single_internal/greetservice.ts:0-0
Timestamp: 2025-01-15T22:33:30.639Z
Learning: In the Wails framework's TypeScript bindings, the import path "/wails/runtime.js" is intentionally absolute and should not be changed to a relative path.

Applied to files:

• v3/internal/runtime/desktop/@wailsio/runtime/package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

• GitHub Check: Run Go Tests v3 (macos-latest, 1.24)
• GitHub Check: Run Go Tests v3 (windows-latest, 1.24)
• GitHub Check: Run Go Tests v3 (ubuntu-latest, 1.24)
• GitHub Check: semgrep/ci
• GitHub Check: Analyze (go)
• GitHub Check: semgrep-cloud-platform/scan

🔇 Additional comments (1)

v3/internal/runtime/desktop/@wailsio/runtime/package.json (1)

4-4: Approve version bump—consistency verified.
v3/internal/runtime/desktop/@wailsio/runtime/package.json is now at 3.0.0-alpha.69; no lingering “3.0.0-alpha.68” references or lockfile mismatches detected.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch atterpac-npm-patch

---

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

[cloudflare-workers-and-pages]

Deploying wails with    Cloudflare Pages

Latest commit:	37905b6
Status:	🚫  Build failed.

View logs

[dosubot]

Related Documentation

Checked 1 published document(s). No updates required.

^{How did I do? Any feedback?}  

[github-actions]

⚠️ Missing Changelog Update

Hi @atterpac, please update v3/UNRELEASED_CHANGELOG.md with a description of your changes.

This helps us keep track of changes for the next release.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud