Skip to main content

​
🚀 Features

​
🔔 Notable Changes

  • Remove identity provider permissions from the Workspace DBA role.
  • Remove support for URL-based secret retrieval via URL template format.
  • Deprecate changelist feature.
  • Add character length limits to prevent overly long entries and ensure data consistency. Length limits applied:
    • 200 characters: Titles and names (groups, issues, plans, projects, instances, users, etc.)
    • 1,000 characters: Short descriptions (group descriptions, operation reasons for cancel/skip/restart tasks)
    • 10,000 characters: Long descriptions (issue details, plan details)
    • 65,536 characters: Comments and long-form text (issue comments)
  • Update APP_IM configuration format in API and UI. Before: 
    {
    "slack": {
        "enabled": true,
        "token": "xxx"
    },
    "lark": {
        "enabled": true,
        ...
    },
    "feishu": {
        "enabled": true,
        ...
    }
}
    After: 
    {
    "settings": [
        {
            "type": "slack",
            "slack": {"token": "xxx"}
        },
        {
            "type": "lark",
            "lark": {}
        }
    ]
}
  • Allow direct data export in SQL Editor for users who can run the query — no approval issue is created. The approval flow still applies to export requests submitted through Data Export Center. You can also disable data export at the workspace level, so that SQL Editor queries cannot be exported directly by default.

​
🎄 Enhancements

  • Issue comment editor now supports searching and linking to other issues within the same project.
  • Support data export for multi-statement queries in SQL Editor.
  • Enhance SSO state management to align with OAuth 2.0 best practices.
  • Add 5-minute expiration for MFA temporary tokens.
  • Clarify label types with explicit naming: Project Labels, Issue Labels, Database Labels.

​
🐞 Bug Fixes

  • Fix the role selector reverting SQL edits during edit mode when the issue poller runs.
  • Fix the false positive Primary Key missing error during SQL Review when adding a PK in a separate statement for PostgreSQL.

​
⚙️ Install and Upgrade

Before upgrading: 1) Back up the metadata — in-place downgrade is not supported. 2) Do not run multiple containers on the same data directory. 3) Terraform users: upgrade Bytebase server first, then apply the new Terraform config.