Skip to content

chore(deps): update dependency supabase to v2.33.9 #2955

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency supabase to v2.33.9 #2955

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 9, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
supabase (source) 2.31.7 -> 2.33.9 age confidence

Release Notes

supabase/cli (supabase)

v2.33.9

Compare Source

Changelog

Bug fixes
Others

v2.33.8

Compare Source

Changelog

Bug fixes
Others

v2.33.7

Compare Source

Changelog

Bug fixes

v2.33.6

Compare Source

Changelog

Bug fixes
Others

v2.33.5

Compare Source

Changelog

Bug fixes

v2.33.4

Compare Source

Changelog

Bug fixes

v2.33.3

Compare Source

Changelog

Bug fixes
Others

v2.33.2

Compare Source

Changelog

Bug fixes
Others

v2.33.1

Compare Source

Changelog

Bug fixes
Others

v2.33.0

Compare Source

Changelog

Features
Others

v2.32.0

Compare Source

Changelog

Features

v2.31.8

Compare Source

Changelog

Bug fixes
Others

Configuration

📅 Schedule: Branch creation - Only on Sunday and Saturday ( * * * * 0,6 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner August 9, 2025 12:48
@renovate renovate bot requested review from hoshinotsuyoshi, FunamaYukina, junkisai, MH4GF and NoritakaIkeda and removed request for a team August 9, 2025 12:48
@vercel Vercel
Copy link

vercel bot commented Aug 9, 2025 •
edited
Loading

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

Project Deployment Preview Comments Updated (UTC)
liam-app Ready Ready Preview Comment Aug 15, 2025 6:07pm
liam-docs Ready Ready Preview Comment Aug 15, 2025 6:07pm
liam-storybook Ready Ready Preview Comment Aug 15, 2025 6:07pm
1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
liam-erd-sample Skipped Skipped Aug 15, 2025 6:07pm

@vercel vercel bot temporarily deployed to Preview – liam-erd-sample August 9, 2025 12:48 Inactive
@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Aug 9, 2025 •
edited
Loading

⚠️ No Changeset found

Latest commit: db4f705

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 9, 2025 •
edited
Loading

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Aug 9, 2025 •
edited
Loading

🤖 Agent Deep Modeling Execution

Started at: 2025-08-15 18:04:36 UTC

Command Output


> @liam-hq/[email protected] execute-deep-modeling /home/runner/work/liam/liam/frontend/internal-packages/agent
> tsx scripts/executeDeepModelingProcess.ts


✅ [INFO] 2025-08-15T18:04:39.109Z Starting Deep Modeling process execution (log level: INFO)

✅ [INFO] 2025-08-15T18:04:39.182Z Starting Deep Modeling workflow execution...

✅ [INFO] 2025-08-15T18:04:39.241Z Request: Design a business management system database with the following core requirements:

1. **Organization Structure**:
   - Hierarchical organizations with self-referencing parent-child relationships
   - Each organization has a unique code and name

2. **Position & Employee Management**:
   - Position master table with unique position codes and names
   - Employee master table with employee codes and names
   - Employee affiliations linking employees to organizations and positions
   - Support for reporting relationships (employees reporting to other employees)

3. **Business Partner System**:
   - Unified business partner table for both clients and suppliers
   - Business partner categories with CHECK constraints (CLIENT/SUPPLIER)
   - Client-specific data with order amounts from last year
   - Supplier-specific data with procurement amounts from last year

4. **Product Management**:
   - Brand master table with unique brand names
   - Item categories for product classification
   - Items with manufacturer part numbers as primary keys
   - Items linked to brands and categories
   - Supplier-brand handling relationships

Please design a normalized database schema with proper primary keys, foreign key relationships, and constraints to support these business operations effectively.

✅ [INFO] 2025-08-15T18:13:25.934Z AI response: Generated 16 use cases for testing and validation

✅ [INFO] 2025-08-15T18:16:16.816Z AI response: Generated 16 use cases for testing and validation

✅ [INFO] 2025-08-15T18:16:17.914Z AI response: Generated 16 use cases for testing and validation

✅ [INFO] 2025-08-15T18:16:47.432Z AI response: Summary of the database design workflow

Main user requirements analyzed:
- Organization structure: hierarchical organizations with unique code/name and self-referencing parent-child.
- Position & employee management: position and employee masters with unique codes/names, employee reporting (supervisor), and employee affiliations to orgs and positions.
- Business partner system: unified partner master with category CHECK (CLIENT/SUPPLIER), and category-specific client/supplier detail data (last-year amounts).
- Product management: brand master (unique name), item categories, items keyed by MPN linked to brand and category, and supplier–brand handling relationships.

Key database design decisions:
- Used UUID primary keys for most entities; items use MPN as the natural primary key.
- Implemented self-referencing FKs for organization parent and employee supervisor with CHECKs preventing self-reference and sensible delete behaviors.
- Normalized category-specific partner data into separate tables (client_details, supplier_details) and enforced correctness via composite FKs (partner_id, category) and a UNIQUE(id, category) on business_partners.
- Modeled many-to-many relationships via junction tables: employee_affiliations and supplier_brand_handling (with CHECK to ensure only SUPPLIER partners can link to brands).
- Enforced uniqueness on business identifiers (org code/name, position code/name, brand name), and non-negative numeric constraints for last-year amounts.
- Added indexes on foreign keys to support query performance.

Schemas/tables created:
- Organization & HR: organizations, positions, employees, employee_affiliations.
- Business partners: business_partners (CHECK category IN ('CLIENT','SUPPLIER'), UNIQUE(id, category)), client_details, supplier_details.
- Products: brands, item_categories, items (PK mpn), supplier_brand_handling.

Important outcomes/results:
- Resolved initial DDL validation error by adding UNIQUE(id, category) to support composite foreign keys from detail and junction tables.
- All constraints and relationships (PKs, FKs, UNIQUE, CHECKs) implemented to meet 3NF and integrity goals.
- Schema successfully validated and applied (all DDL executed); requirements saved to artifact.

✅ [INFO] 2025-08-15T18:16:47.455Z Deep Modeling workflow completed successfully

✅ [INFO] 2025-08-15T18:16:47.455Z Session ID: 5101d686-7b73-40b3-8ef1-288bbd6343ca

✅ [INFO] 2025-08-15T18:16:47.455Z To resume this session later, use: --session-id 5101d686-7b73-40b3-8ef1-288bbd6343ca

✅ [INFO] 2025-08-15T18:16:47.455Z Workflow Messages:

✅ [INFO] 2025-08-15T18:16:47.455Z   1. [human] Design a business management system database with the following core requirements:

1. **Organization Structure**:
   - Hierarchical organizations with self-referencing parent-child relationships
   -...

✅ [INFO] 2025-08-15T18:16:47.455Z   2. [ai] Planned actions:
- Structure the user’s request into a concise BRD with clear, testable requirements.
- Identify core entities and required relationships based strictly on provided details.
- Specify ...

✅ [INFO] 2025-08-15T18:16:47.456Z   3. [tool] Requirements saved successfully to artifact

✅ [INFO] 2025-08-15T18:16:47.456Z   4. [ai] Requirements analysis complete and saved to artifact.

✅ [INFO] 2025-08-15T18:16:47.456Z   5. [ai] Planning checklist:
- Create core master tables: organizations, positions, employees, brands, item_categories
- Add relationship and junction tables: employee_affiliations, supplier_brand_handling
- I...

❌ [ERROR] 2025-08-15T18:16:47.456Z   6. [tool] Error: DDL execution validation failed: SQL: ALTER TABLE "client_details" ADD CONSTRAINT "fk_client_details_partner_category" FOREIGN KEY ("partner_id", "category") REFERENCES "business_partners" ("id...

✅ [INFO] 2025-08-15T18:16:47.456Z   7. [ai] Purpose: Recreate the full normalized schema, adding a UNIQUE(id, category) on business_partners to satisfy composite foreign keys from client_details, supplier_details, and supplier_brand_handling. M...

✅ [INFO] 2025-08-15T18:16:47.456Z   8. [tool] Schema successfully updated. The operations have been applied to the database schema, DDL validation successful (108/108 statements executed successfully), and new version created.

✅ [INFO] 2025-08-15T18:16:47.456Z   9. [ai] Status: All requested schema objects created and validated.

Summary of what was done:
- Built master tables: organizations, positions, employees, brands, item_categories, items
- Established relation...

✅ [INFO] 2025-08-15T18:16:47.456Z   10. [ai] Generated 16 use cases for testing and validation

✅ [INFO] 2025-08-15T18:16:47.456Z   11. [ai] Summary of the database design workflow

Main user requirements analyzed:
- Organization structure: hierarchical organizations with unique code/name and self-referencing parent-child.
- Position & emp...

✅ [INFO] 2025-08-15T18:16:47.456Z RESULT: 11 tables created - organizations, positions, employees, employee_affiliations, business_partners, client_details, supplier_details, brands, item_categories, items, supplier_brand_handling

✅ [INFO] 2025-08-15T18:16:47.456Z Deep Modeling session completed successfully

✅ Status: Completed successfully

Finished at: 2025-08-15 18:16:48 UTC

@renovate renovate bot force-pushed the renovate/supabase-2.x branch from 9453885 to 4b75254 Compare August 9, 2025 17:36
@vercel vercel bot temporarily deployed to Preview – liam-erd-sample August 9, 2025 17:36 Inactive
@renovate renovate bot force-pushed the renovate/supabase-2.x branch from 4b75254 to bb08e7f Compare August 10, 2025 12:31
@vercel vercel bot temporarily deployed to Preview – liam-erd-sample August 10, 2025 12:31 Inactive
@renovate renovate bot force-pushed the renovate/supabase-2.x branch from bb08e7f to dfcdf20 Compare August 12, 2025 09:37
@renovate renovate bot changed the title chore(deps): update dependency supabase to v2.33.2 chore(deps): update dependency supabase to v2.33.3 Aug 12, 2025
@vercel vercel bot temporarily deployed to Preview – liam-erd-sample August 12, 2025 09:37 Inactive
@renovate renovate bot changed the title chore(deps): update dependency supabase to v2.33.4 chore(deps): update dependency supabase to v2.33.5 Aug 12, 2025
@vercel vercel bot temporarily deployed to Preview – liam-erd-sample August 12, 2025 18:40 Inactive
@renovate renovate bot force-pushed the renovate/supabase-2.x branch from 3f53eda to d4dc742 Compare August 13, 2025 08:28
@renovate renovate bot changed the title chore(deps): update dependency supabase to v2.33.5 chore(deps): update dependency supabase to v2.33.6 Aug 13, 2025
@vercel vercel bot temporarily deployed to Preview – liam-erd-sample August 13, 2025 08:28 Inactive
@renovate renovate bot force-pushed the renovate/supabase-2.x branch from d4dc742 to 2fb8db5 Compare August 13, 2025 13:39
@vercel vercel bot temporarily deployed to Preview – liam-erd-sample August 13, 2025 13:39 Inactive
@renovate renovate bot changed the title chore(deps): update dependency supabase to v2.33.6 chore(deps): update dependency supabase to v2.33.7 Aug 13, 2025
@renovate renovate bot force-pushed the renovate/supabase-2.x branch from 2fb8db5 to 7ae1f43 Compare August 14, 2025 08:56
@vercel vercel bot temporarily deployed to Preview – liam-erd-sample August 14, 2025 08:56 Inactive
@renovate renovate bot changed the title chore(deps): update dependency supabase to v2.33.7 chore(deps): update dependency supabase to v2.33.8 Aug 14, 2025
@renovate renovate bot force-pushed the renovate/supabase-2.x branch from 7ae1f43 to db4f705 Compare August 15, 2025 18:00
@renovate renovate bot changed the title chore(deps): update dependency supabase to v2.33.8 chore(deps): update dependency supabase to v2.33.9 Aug 15, 2025
@vercel vercel bot temporarily deployed to Preview – liam-erd-sample August 15, 2025 18:00 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hoshinotsuyoshi hoshinotsuyoshi Awaiting requested review from hoshinotsuyoshi hoshinotsuyoshi is a code owner automatically assigned from liam-hq/liam-dev

@FunamaYukina FunamaYukina Awaiting requested review from FunamaYukina FunamaYukina is a code owner automatically assigned from liam-hq/liam-dev

@junkisai junkisai Awaiting requested review from junkisai junkisai is a code owner automatically assigned from liam-hq/liam-dev

@MH4GF MH4GF Awaiting requested review from MH4GF MH4GF is a code owner automatically assigned from liam-hq/liam-dev

@NoritakaIkeda NoritakaIkeda Awaiting requested review from NoritakaIkeda NoritakaIkeda is a code owner automatically assigned from liam-hq/liam-dev

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants