chore(main): release vynta-app 1.1.2

[daiv05]

🤖 I have created a release beep boop

1.1.2 (2026-03-09)

Bug Fixes

• branch correction for updating to update Cargo.lock (7ad4895)
• magnifier and release please config (ac7f760)
• magnifier motor/mode improvements (e6c784b)
• release please config (4f2f0ca)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• Bug Fixes

  • Fixed magnifier configuration and mode issues reported in the prior release.

• Chores / Release

  • Bumped app version to 1.1.2 and added a corresponding changelog entry.
  • Updated release workflow and packaging metadata to streamline future releases.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vynta	Ready	Preview, Comment	Mar 9, 2026 9:49pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d793048a-ee9b-4835-bc99-ebeac5165a6b

📥 Commits

Reviewing files that changed from the base of the PR and between 76ef3a2 and 319dcef.

⛔ Files ignored due to path filters (1)

• src-tauri/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• .github/workflows/release-please.yml

---

📝 Walkthrough

Walkthrough

This PR bumps the project version from 1.1.1 to 1.1.2 across manifests and configs, adds a 1.1.2 changelog entry, and adjusts the release-please GitHub Actions workflow (branch extraction, fetch/checkout, lockfile generation/path, and push behavior).

Changes

Cohort / File(s)	Summary
Release manifest & changelog /.github/release-please-manifest.json, CHANGELOG.md	Manifest version key updated to 1.1.2; new CHANGELOG entry for 1.1.2 listing bug-fix commits.
Project metadata package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json, src-tauri/tauri.microsoftstore.conf.json	Version fields changed from 1.1.1 → 1.1.2 across package and tauri configuration files.
CI / Release workflow .github/workflows/release-please.yml	Adjusted branch extraction to use prs[0].headBranchName, changed git fetch/checkout usage, replaced cargo update with cargo generate-lockfile, staged src-tauri/Cargo.lock, and switched push to git push origin "$BRANCH".

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• fix: magnifier and release please config #6: Makes similar release-please workflow changes (lockfile handling and branch extraction) — strong overlap with CI edits.
• chore(main): release vynta-app 1.1.0 #3: Performs version bumps and changelog updates for release versions — matches metadata changes here.
• chore(main): release vynta-app 1.1.1 #5: Another release/version bump PR touching the same manifest and config files.

Poem

🐰 I bumped the numbers, hopped through each file,

From one-one-one to one-one-two in a mile.
Manifests tidy, changelog in tow,
CI adjusted — off we go! ✨ 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(main): release vynta-app 1.1.2' accurately describes the primary change: a version bump release from 1.1.1 to 1.1.2 across all configuration files and manifests.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-please--branches--main--components--vynta-app

---

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

[daiv05]

🤖 Created releases:

• vynta-app-v1.1.2

🌻