Skip to content

Upgrades: GitHub Actions v7, tooling, drop unused react-pdf - #61

Merged
Axoineo merged 2 commits into
mainfrom
chore/upgrades
Nov 19, 2026
Merged

Axoineo merged 2 commits into
mainfrom
chore/upgrades

Conversation

@Axoineo

@Axoineo Axoineo commented Nov 19, 2026 •

Copy link
Copy Markdown
Owner

Replaces Dependabot #24, #25, #26 (except Tailwind CSS 4), #28 and #60 (hono 4.13.19).

  • GitHub Actions checkout and setup-node v4 to v7. Only affects the automatic checks.
  • Tooling: Cloudflare vite plugin 1.70, React plugin 6.3, oxlint 1.94, Supabase CLI 3.2.
  • react-pdf removed: nothing imports it; pdfjs-dist stays for scripts/pdf.
  • Not included: Tailwind CSS 4. It changes how all styling is built (new PostCSS plugin and config) and is what broke chore(deps-dev): bump the dev-tooling group across 1 directory with 7 updates #26's build. It needs its own migration and a visual check of every page.

Checked: npm run check (343 tests, build, secret scan), npm audit --omit=dev 0 vulnerabilities, Supabase CLI starts, and the built CSS is byte-for-byte the same as the live build, so the site looks the same.

🤖 Generated with Claude Code

- actions/checkout and actions/setup-node v4 to v7 (Dependabot #24, #25).
- @cloudflare/vite-plugin 1.70, @vitejs/plugin-react 6.3, oxlint 1.94 and the
  Supabase CLI 3.2 from the dev-tooling group (#26). Tailwind CSS 4 is left out:
  it is a styling migration of its own (new PostCSS plugin, config and base-style
  changes), and it is what failed #26's build.
- react-pdf removed instead of upgraded (#28): nothing in the code imports it.
  pdfjs-dist stays for the scripts in scripts/pdf.

npm run check passes (343 tests, build, secret scan); npm audit --omit=dev finds
0 vulnerabilities; the built CSS is byte-for-byte the same as main's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-19T08:20:59.289625Z 4589412 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

Deploying dikho with  Cloudflare Pages  Cloudflare Pages

Latest commit: d730b23
Status: ✅  Deploy successful!
Preview URL: https://1bed9ca6.dikho.pages.dev
Branch Preview URL: https://chore-upgrades.dikho.pages.dev

View logs

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Axoineo
Axoineo merged commit 669a8c2 into main Nov 19, 2026
9 checks passed
@Axoineo
Axoineo deleted the chore/upgrades branch November 19, 2026 08:19

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4589412b9e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread package.json
"supabase": "^2.118.0-beta.55",
"@vitejs/plugin-react": "^6.3.0",
"oxlint": "^1.94.0",
"supabase": "^3.2.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep migration commands targeting the hosted database

When operators follow the existing APPLY: npx supabase db push instruction (for example, in supabase/migrations/20260927000000_turnstile_lockdown.sql:36), CLI v3 targets the local stack unless --remote is passed; hosted changes also need confirmation, including --yes in non-interactive runs. With a local stack running, the documented command can succeed against the wrong database and leave the production lockdown unapplied. Update the migration instructions to use the v3 flags or keep the CLI on v2; the Supabase CLI v3 migration guide documents these target and confirmation changes.

Useful? React with 👍 / 👎.

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.

1 participant