updated release notes date, onboarding screen for v0.12.3

[sawka]

No description provided.

[coderabbitai]

Walkthrough

This pull request implements a version bump of the onboarding system from v0.12.2 to v0.12.3. The changes include: updating the version constant, creating a new upgrade onboarding content component describing Wave AI updates, terminal improvements, and secret store features, integrating the new version into the upgrade patch configuration, refactoring hard-coded version thresholds to use a centralized constant, and updating the release notes date.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• UpgradeOnboardingModal_v0_12_3_Content component — New UI component needs verification for correct content structure, icon usage, and alignment with design patterns
• onboarding-upgrade-patch.tsx configuration — Verify v0.12.3 entry is correctly linked to the new component and navigation connections between v0.12.2 and v0.12.3 are properly bidirectional
• onboarding-upgrade.tsx refactoring — Confirm CurrentOnboardingVersion constant replaces all hard-coded thresholds consistently and doesn't introduce any unintended control flow changes
• Version coordination — Ensure the version bump is consistently applied across all five affected files with no misalignment

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No description was provided by the author, which is not related to the changeset.	Add a description explaining the changes made, such as the release notes update and new onboarding screen features.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main changes: updating release notes date and adding a v0.12.3 onboarding screen.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch sawka/rl-123-2

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 125cf98 and 92697c3.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• docs/docs/releasenotes.mdx (1 hunks)
• frontend/app/onboarding/onboarding-common.tsx (1 hunks)
• frontend/app/onboarding/onboarding-upgrade-patch.tsx (2 hunks)
• frontend/app/onboarding/onboarding-upgrade-v0123.tsx (1 hunks)
• frontend/app/onboarding/onboarding-upgrade.tsx (2 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-10-21T05:09:26.916Z

Learnt from: sawka
Repo: wavetermdev/waveterm PR: 2465
File: frontend/app/onboarding/onboarding-upgrade.tsx:13-21
Timestamp: 2025-10-21T05:09:26.916Z
Learning: The onboarding upgrade modal in frontend/app/onboarding/onboarding-upgrade.tsx intentionally freezes the lastVersion at mount using a ref to prevent the modal from changing or disappearing mid-interaction when the user is going through the onboarding flow.

Applied to files:

• frontend/app/onboarding/onboarding-common.tsx
• frontend/app/onboarding/onboarding-upgrade.tsx
• frontend/app/onboarding/onboarding-upgrade-patch.tsx
• frontend/app/onboarding/onboarding-upgrade-v0123.tsx

🧬 Code graph analysis (2)

frontend/app/onboarding/onboarding-upgrade.tsx (1)

frontend/app/onboarding/onboarding-common.tsx (1)

• CurrentOnboardingVersion (4-4)

frontend/app/onboarding/onboarding-upgrade-patch.tsx (1)

frontend/app/onboarding/onboarding-upgrade-v0123.tsx (1)

• UpgradeOnboardingModal_v0_12_3_Content (84-84)

⏰ 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). (5)

• GitHub Check: Build Docsite
• GitHub Check: Analyze (go)
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Build for TestDriver.ai
• GitHub Check: merge-gatekeeper

🔇 Additional comments (8)

docs/docs/releasenotes.mdx (1)

9-9: LGTM - Release date updated.

The date update aligns with the PR creation date and other version bumps in this release.

frontend/app/onboarding/onboarding-upgrade-patch.tsx (2)

19-19: LGTM - Import added for v0.12.3 content.

The import correctly references the new v0.12.3 onboarding content component.

---

38-44: LGTM - Version configuration properly extended.

The v0.12.3 entry follows the established pattern and correctly wires up bidirectional navigation between v0.12.2 and v0.12.3.

frontend/app/onboarding/onboarding-common.tsx (1)

4-4: LGTM - Version constant bumped to v0.12.3.

The centralized version constant has been correctly updated to reflect the new release.

frontend/app/onboarding/onboarding-upgrade.tsx (2)

9-9: Excellent refactoring - centralized version constant.

Good improvement to use the centralized CurrentOnboardingVersion constant instead of hard-coded version strings.

---

24-29: LGTM - Version threshold now uses centralized constant.

Both version checks now correctly reference the centralized constant, eliminating duplicate hard-coded version strings and making future updates easier.

frontend/app/onboarding/onboarding-upgrade-v0123.tsx (2)

4-80: LGTM - Well-structured onboarding content for v0.12.3.

The content accurately reflects the release notes and follows the established pattern from previous version onboarding components. All key features (GPT-5.1, Thinking Mode Toggle, Enhanced Input Handling, Image Paste Support, Secret Store) are properly highlighted.

---

82-84: LGTM - Component properly exported.

The component is correctly exported with a displayName, following the pattern established by other version-specific onboarding components.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining why this PR is needed, why this solution was chosen, and what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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