Fix docs deployment: switch from npm to Bun#306
Conversation
package-lock.json was deleted in #303. The deploy workflow used npm ci with cache-dependency-path: package-lock.json, causing all deployments to fail since the Bun migration. Switch to bun install --frozen-lockfile, remove Node setup (Bun handles everything). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 2 minutes and 1 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Pages docs deployment workflow to align with the repository’s Bun-based package management so the workflow no longer relies on a removed package-lock.json.
Changes:
- Replaced
npm ciwithbun install --frozen-lockfilefor monorepo dependency installation. - Removed the
actions/setup-nodestep from the docs deploy workflow. - Simplified the monorepo build step from
make alltomake(default target).
Comments suppressed due to low confidence (1)
.github/workflows/deploy-docs.yml:40
tko.io'sbuildscript invokes theastroCLI withNODE_OPTIONS=--experimental-strip-types, andprebuildexplicitly runsnode ...(seetko.io/package.json). Removingactions/setup-nodemeans this workflow now depends on whatever Node version happens to be preinstalled onubuntu-latest, which can break the docs build if that Node version doesn’t support the requiredNODE_OPTIONSflag. Consider restoringactions/setup-node(without npm caching) and pinning a Node version known to work for the docs build (e.g. 22+), or refactoring the docs scripts to avoid requiring thenodebinary/Node-specific flags.
- name: Setup Bun
uses: oven-sh/setup-bun@v2
- name: Install monorepo dependencies
run: bun install --frozen-lockfile
- name: Build monorepo packages
run: make
- name: Install site dependencies
run: cd tko.io && bun install --frozen-lockfile
- name: Build site
run: cd tko.io && bun run build
release.yml used npm ci which requires the deleted package-lock.json. Switch to bun install --frozen-lockfile. Keep Node/npm for changeset publishing (npm OIDC trusted publishing requires npm CLI). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Summary
The docs deploy workflow (
deploy-docs.yml) has been failing since the Bun migration (#303) because it usesnpm ciwithcache-dependency-path: package-lock.json— butpackage-lock.jsonwas deleted.Switch to
bun install --frozen-lockfileand remove the Node setup step.Test plan
🤖 Generated with Claude Code