chore: add workflow to update supabase-js#377
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughAdds a new GitHub Actions workflow "Update Sequence Diagram(s)sequenceDiagram
participant Trigger as User / Scheduler
participant Actions as GitHub Actions
participant Repo as Repository (website workspace)
participant GHAPI as GitHub API
Trigger->>Actions: start workflow(version, source)
Actions->>Repo: checkout main
Actions->>Actions: setup Node.js 20 + pnpm cache
Actions->>Repo: update `@supabase/supabase-js` version\nrefresh lockfile
Actions->>GHAPI: request GitHub App token
GHAPI-->>Actions: return token
Actions->>Repo: create branch gha/auto-update-supabase-js-v<version>\ncommit changes
Actions->>Repo: push branch
Actions->>GHAPI: create pull request to main\n(with commit message/body including source & version)
GHAPI-->>Actions: PR created
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.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/update-supabase-js.yml:
- Around line 25-27: Replace hardcoded "ref: main" values used with the checkout
action and the PR creation step by referencing the repository's default branch
dynamically (replace both occurrences of "ref: main" near the
actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 invocation and the
later PR creation step) using the expression like ref: ${{
github.event.repository.default_branch }} so the workflow targets the repository
default branch rather than assuming "main".
- Around line 29-39: The workflow uses npm and website/package-lock.json but the
repo uses pnpm; update the "Setup Node.js" step to use cache: "pnpm" and
cache-dependency-path: website/pnpm-lock.yaml, and change the "Update
`@supabase/supabase-js` to latest" step to run pnpm (e.g., pnpm add
`@supabase/supabase-js`@${{ inputs.version }} in the website working-directory) so
the workflow aligns with the pnpm lockfile; adjust only those fields and the
install command in the referenced steps.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Central YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
Run ID: a2d945bf-6ef8-42af-b569-55b7a3443991
📒 Files selected for processing (1)
.github/workflows/update-supabase-js.yml
641230a to
4dc90d2
Compare
4dc90d2 to
6074270
Compare
6074270 to
430343f
Compare
430343f to
25f879b
Compare
Worklfow that will update supabase-js package.