Skip to content

[pull] main from bytebase:main#466

Merged
pull[bot] merged 3 commits intoxfworld:mainfrom
bytebase:main
Feb 7, 2026
Merged

[pull] main from bytebase:main#466
pull[bot] merged 3 commits intoxfworld:mainfrom
bytebase:main

Conversation

@pull
Copy link

@pull pull bot commented Feb 7, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

vsai12 and others added 3 commits February 7, 2026 10:53
… checks (#19266)

DROP VIEW was incorrectly classified as DROP_TABLE in the PostgreSQL and
Redshift statement type parsers (legacy compat with old pg_query_go parser).
This caused non-materialized views to be marked as HIGH risk, triggering
approval workflows unnecessarily. Non-materialized views hold no data, so
dropping them is not destructive.

Changes:
- Parser: DROP VIEW now maps to DROP_VIEW (not DROP_TABLE)
- Parser: DROP MATERIALIZED VIEW stays as DROP_TABLE (holds data)
- Advisor: SCHEMA_BACKWARD_COMPATIBILITY no longer flags DROP VIEW
- Both PostgreSQL and Redshift parsers updated

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…tance in SaaS mode (#19267)

* fix(frontend): fix GCP IAM credentials not sent when creating new instance in SaaS mode

The `credentialSource` watcher that sets `iamExtension` on the data source
was not `immediate`, so it missed the value change made by the earlier
`isDefaultCredentialDisabled` watcher during component setup. This caused
GCP/AWS/Azure IAM credentials to never be initialized on new instance
creation in SaaS mode, falling back to default credentials which don't
exist.

Regression from #18161 which added the SaaS mode credential restriction.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: remove unused parameter to pass eslint check

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: format ternary to satisfy biome

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* feat: remove auto_enable_backup from project settings

Backup should be turned on explicitly by users since not all DMLs are data fixes.
The backup feature is primarily used for data fixes with a few line changes.

Changes:
- Removed auto_enable_backup from proto/v1/v1/project_service.proto
- Removed auto_enable_backup from proto/store/store/project.proto
- Updated backend api and converters to remove the field
- Updated frontend project settings panel to remove the switch
- Updated plan initialization to default enablePriorBackup to false
- Updated telemetry to remove auto_enable_backup reference
- Removed auto-enable-backup from all locale files

* feat: remove prior backup telemetry

Since auto_enable_backup is removed, the telemetry for tracking its usage
relative to project settings is no longer needed.
@pull pull bot locked and limited conversation to collaborators Feb 7, 2026
@pull pull bot added the ⤵️ pull label Feb 7, 2026
@pull pull bot merged commit af086ee into xfworld:main Feb 7, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants