Skip to content

chore: add workflow to update supabase-js#377

Merged
mandarini merged 1 commit intomasterfrom
chore/update-supabase-workflow
Mar 4, 2026
Merged

chore: add workflow to update supabase-js#377
mandarini merged 1 commit intomasterfrom
chore/update-supabase-workflow

Conversation

@mandarini
Copy link
Contributor

Worklfow that will update supabase-js package.

@vercel
Copy link

vercel bot commented Mar 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
dbdev Ready Ready Preview, Comment Mar 4, 2026 0:05am

Request Review

@supabase
Copy link

supabase bot commented Mar 4, 2026

This pull request has been ignored for the connected project xmuptpplfviifrbwmmtv because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@coderabbitai
Copy link

coderabbitai bot commented Mar 4, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 935e453c-320d-45a5-b460-6a30ae9582b5

📥 Commits

Reviewing files that changed from the base of the PR and between 641230a and 25f879b.

📒 Files selected for processing (1)
  • .github/workflows/update-supabase-js.yml
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/update-supabase-js.yml

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Added automation to streamline dependency updates for the development workflow.

Walkthrough

Adds a new GitHub Actions workflow "Update @supabase/supabase-js" that automates updating the @supabase/supabase-js dependency. The workflow accepts a required version and optional source (defaults to "manual"). A single job checks out the main branch, sets up Node.js 20 with pnpm caching scoped to the website directory, updates the specified @supabase/supabase-js version in the website workspace and refreshes the lockfile, generates a GitHub App token, and creates a branch gha/auto-update-supabase-js-v<version> with a commit and a pull request to main containing the source and version in the message.

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
Loading

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

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between 335a3ed and 641230a.

📒 Files selected for processing (1)
  • .github/workflows/update-supabase-js.yml

@mandarini mandarini merged commit 965dbd4 into master Mar 4, 2026
8 checks passed
@mandarini mandarini deleted the chore/update-supabase-workflow branch March 4, 2026 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants