fix: Update deployment

[pabloderen]

Summary by CodeRabbit

• Chores
  • Implemented automated CI/CD pipeline using GitHub Actions for continuous builds on main branch
  • Configured semantic-release for automatic version management and release artifact generation
  • Release process now handles automated packaging, versioning updates, and distribution

[coderabbitai]

Walkthrough

Introduces CI/release automation infrastructure by adding a GitHub Actions workflow, semantic-release configuration file, a manifest version update script, and related development dependencies to automate building, packing, and publishing releases on the main branch.

Changes

Cohort / File(s)	Summary
Release Automation Setup .github/workflows/build-pack.yml, .releaserc.json	New CI workflow triggering on main pushes/PRs with build, pack, and semantic-release steps. Release configuration defines plugins for commit analysis, release notes generation, asset publishing via git and GitHub with exec-based manifest version updates.
Dependencies package.json	Added @semantic-release/exec, @semantic-release/git, and semantic-release as development dependencies.
Version Management Script scripts/update-manifest-version.mjs	New Node.js script that reads manifest.json, updates its version field from CLI argument, and writes the file back with proper formatting.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 Hop, hop, the pipeline's set!
Semantic-release, no regret,
Manifests bump with auto-cheer,
Each version flows so crystal clear! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'fix: Update deployment' is vague and generic, using non-descriptive terms that don't clearly convey what the changeset accomplishes.	Replace with a more specific title that describes the actual changes, such as 'feat: Add semantic-release CI/CD workflow and release automation' or 'feat: Implement automated release pipeline with GitHub Actions'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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 docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/Deploy

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

scripts/update-manifest-version.mjs (1)

16-19: Resolve manifest.json path to avoid CWD-dependent failures (Line 16).
The script assumes it’s run from the repo root. If invoked from another working directory, it will throw ENOENT. Consider resolving the path relative to the script location.

Proposed fix

 import fs from "node:fs";
+import path from "node:path";
+import { fileURLToPath } from "node:url";

-const file = "manifest.json";
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
+const file = path.resolve(__dirname, "..", "manifest.json");
 const manifest = JSON.parse(fs.readFileSync(file, "utf8"));

.github/workflows/build-pack.yml (1)

38-40: Prefer local semantic-release binary to avoid implicit downloads (Line 40).
npx can fetch a different version if the local install is missing. Using --no-install ensures the workflow uses the pinned devDependency and fails fast if it isn’t present.

Proposed fix

-        run: npx semantic-release
+        run: npx --no-install semantic-release

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀