chore: fix github pages deployment action

[aritra1999]

Attempt 4

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the CI/CD workflow to use Bun instead of Node for package management, including setup tool replacement, install command change, and build command updates. Simplified the prepare script in site/package.json by removing the fallback echo command.

Changes

Cohort / File(s)	Summary
CI/CD Workflow .github/workflows/deploy.yml	Replaced Node-based setup (node-version 20 with npm) with Bun setup (bun-version latest). Updated install step from npm install to bun install and build step from npm run build to sequential bun run prepare and bun run build commands.
Build Configuration site/package.json	Removed fallback || echo '' from the prepare script, changing from svelte-kit sync || echo '' to direct svelte-kit sync command, causing the prepare step to fail on error instead of silently succeeding.

Possibly related PRs

• chore: fix github pages deployment issue  #21: Directly modifies the same prepare script in site/package.json, removing the \|\| echo '' fallback with identical intent.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is vague and non-descriptive, providing only 'Attempt 4' without conveying meaningful information about the changeset.	Replace the placeholder description with details about the specific changes, such as: switching from Node/npm to Bun in CI, updating the prepare script, or fixing the GitHub Pages deployment workflow.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change—migrating the CI workflow from Node/npm to Bun and fixing the GitHub Pages deployment process.
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 chore/landing-and-docs

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

.github/workflows/deploy.yml (2)

24-27: Consider pinning the Bun version for reproducible CI builds.

Using bun-version: latest means the CI runtime can change unexpectedly when a new Bun release drops, potentially causing flaky or broken builds that are hard to diagnose. Pinning to a specific version (e.g., 1.x.y) and updating it intentionally is safer.

       - name: Setup Bun
         uses: oven-sh/setup-bun@v2
         with:
-          bun-version: latest
+          bun-version: "1.2.4"

---

29-30: Use --frozen-lockfile for deterministic CI installs.

Without --frozen-lockfile, bun install may update the lockfile if it drifts from package.json, leading to non-reproducible builds. In CI, you generally want to fail fast if the lockfile is out of sync.

       - name: Install dependencies
-        run: cd site && bun install
+        run: cd site && bun install --frozen-lockfile

---

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