release

[modelorona]

This release adds the option for someone to run a demo in-memory SQLite database

[jazzberry-ai]

An error occured.

_{This error may be due to rate limits. If this error persists, please email us.}

[github-actions]

Hey, leave a @claude-review comment below and I'll do a code review!

[jazzberry-ai]

An error occured.

_{This error may be due to rate limits. If this error persists, please email us.}

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
Inconsistent environment names for Apple build and deploy workflows	High	Trigger a release build that includes Apple deployment.	The _build-apple.yml workflow was updated to use the build-apple environment, but the _deploy-apple.yml workflow still uses the deploy-apple environment. This inconsistency can cause deployment issues as the deploy job might not find the build artifacts.
Incomplete AppImage disablement	Medium	N/A - this is a cleanup issue.	Even though AppImage builds are disabled, the following files and configurations still exist: _build-appimage.yml, build-appimage.sh, commented-out AppImage artifact handling in _sign-validate.yml, and appimage variables and logic in _sign-validate.yml. These should be removed for clarity and to avoid confusion. The comment "DISABLED: AppImage requires system WebKit2GTK" should be added to the README or a similar prominent location.
Potential resource leak in GetSampleDatabase()	Low	Attempt to connect to the sample database multiple times after the initialization fails (e.g., due to a corrupted SQL script).	The GetSampleDatabase() function attempts to open a new connection to the in-memory database every time it's called, even if the initialization failed previously. This could lead to unnecessary resource consumption or unexpected errors.
Potential SQL injection vulnerability in table creation	High	Attempt to create a table with a column name containing malicious SQL code.	The createTableQuery in core/src/plugins/gorm/add.go is constructed dynamically using user-provided column names and data types. If these inputs are not properly sanitized, it could lead to an SQL injection vulnerability.
Missing error handling for orders.status constraint violation	Low	Attempt to insert an order with a status value other than 'pending', 'completed', or 'canceled'.	The orders.status column has a CHECK constraint that limits the allowed values. The application should handle this constraint violation gracefully with appropriate error messaging when attempting to insert an invalid status value.

_{Comments? Email us.}

[jazzberry-ai]

An error occured.

_{This error may be due to rate limits. If this error persists, please email us.}

[jazzberry-ai]

An error occured.

_{This error may be due to rate limits. If this error persists, please email us.}