feat: add one-off release workflow for package publishing

[cherkanovart]

Summary

Add a manually triggered one-off release workflow that publishes packages with the next tag (for bin migration / canary releases).

Changes

• New workflow .github/workflows/one-off-release.yml — Triggered via workflow_dispatch; checks out repo, sets up Node 22 and pnpm, installs dependencies, and runs pnpm changeset publish --tag next with npm provenance.
• Changeset — Patch bump for lingo.dev with message “add 1-off release workflow”.

Testing

Business logic tests added:

• N/A — workflow only; no new application tests.
• All tests pass locally (or: workflow was run manually once to confirm publish with next tag).

Visuals

Required for UI/UX changes:

• Before/after screenshots attached
• Video demo for interactions (< 30s)

N/A — no UI/UX changes.

Checklist

• Changeset added (if version bump needed)
• Tests cover business logic (or N/A for workflow-only change)
• No breaking changes (or documented below)

Closes #--

Summary by CodeRabbit

• Chores
  • Introduced automated release workflow for streamlined package publishing with improved deployment capabilities.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR introduces a one-off release mechanism by adding a GitHub Actions workflow triggered via manual dispatch. The workflow automates dependency setup, package installation, and publishing with the "next" tag. A corresponding changeset file documents this addition.

Changes

Cohort / File(s)	Summary
Release Automation .github/workflows/one-off-release.yml	New GitHub Actions workflow for manual release dispatch with Node.js 22, npm 11.5.1, and pnpm 9.12.3 setup, followed by package publication to npm with next tag and provenance enabled.
Changelog Documentation .changeset/famous-moose-sink.md	New changeset file recording a patch-level release for "lingo.dev" and documenting the addition of the one-off release workflow feature.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A button to press, a workflow so neat,
Automates releases, quick and sweet!
With pnpm's grace and npm's might,
One-off deployments done right. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a one-off release workflow for package publishing, which aligns with the core purpose of this PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The pull request description comprehensively covers all required sections: summary, changes, testing (with N/A rationale), visuals (N/A), and checklist with appropriate completion.

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

✨ 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 feat/add-temp-workflow

---

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