Skip to content

chore(repo): adopt hybrid Bun catalogs and exclude examples from root lint#109

Merged
lentil32 merged 3 commits intomainfrom
betterthing
Apr 16, 2026
Merged

chore(repo): adopt hybrid Bun catalogs and exclude examples from root lint#109
lentil32 merged 3 commits intomainfrom
betterthing

Conversation

@lentil32
Copy link
Copy Markdown
Contributor

One-Line Summary

Centralize shared workspace dependency versions with a hybrid Bun catalog layout and stop root lint from treating standalone examples as workspace code.

User-Facing Changes

  • Shared dependency versions used across apps/* and packages/* now come from Bun catalog / catalogs references instead of repeated inline pins.
  • Bun version pins are aligned to 1.3.11 in the repo config.
  • Root type-aware lint now ignores examples/**, so standalone demos no longer block unrelated pushes.

Why This Changed

Version management in the workspace was only partially cataloged, which meant common dependency bumps still required repeated manifest edits.

The repo also runs root oxlint . during pre-push. examples/auto-debug-demo is intentionally outside workspaces.packages, so root installs do not manage its dependencies, but root lint was still type-checking it. That caused unrelated pushes to fail on unresolved hono / postgres imports inside a standalone example.

How It Changed

  • Kept shared runtime dependencies in the default Bun catalog and split testing and tooling dependencies into catalogs.testing and catalogs.tooling.
  • Repointed workspace manifests to catalog:, catalog:testing, or catalog:tooling as appropriate.
  • Moved @types/pg in @onequery/server from dependencies to devDependencies.
  • Aligned .bun-version, packageManager, and @types/bun to 1.3.11.
  • Added examples/** to the root oxlint ignore list with a note that examples are outside the main workspace graph.

Bug Fixes

  • Under repo pre-push lint, standalone example files were type-checked without their own installed dependencies, which produced unresolved module errors and blocked pushes. Root lint now excludes those directories.

Extra Context / Decisions

  • I validated formatting and the exact pre-push lint path in the current shell.
  • The active local Bun binary in this session was still 1.3.10 while the repo now pins 1.3.11, so I did not use this session to refresh installs against the newly pinned runtime.

Verification

  • bun run format
  • bunx turbo lint --json -- --type-aware --type-check

Video / Screenshot (Optional)

  • N/A

@lentil32 lentil32 requested a review from siisee11 as a code owner April 16, 2026 05:51
@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Apr 16, 2026

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
onequery-landing d348d5f Commit Preview URL

Branch Preview URL
Apr 16 2026, 05:59 AM

Copy link
Copy Markdown

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

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: 5d6e63612b

ℹ️ 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
@lentil32 lentil32 merged commit f230f49 into main Apr 16, 2026
7 checks passed
@lentil32 lentil32 deleted the betterthing branch April 16, 2026 06:01
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