Skip to content

remove expandable part cicd for 3.14.0 #1012

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

Open
adela-bytebase wants to merge 2 commits into
base: main
Choose a base branch
from
+1 −3
Open

remove expandable part cicd for 3.14.0 #1012

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b2c75df
remove expandable part cicd for 3.14.9
adela-bytebase Feb 5, 2026
77a33e8
fix
adela-bytebase Feb 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions docs/changelog/bytebase-3-14-0.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,11 @@ import InstallUpgrade from '/snippets/install/install-upgrade.mdx';
## 🌟 Sequel to New CI/CD Experience

- Database **CI (review)** and **CD (deployment)** are 2 separated phases, aligning with industry standard CI/CD practices (GitHub, GitLab):
<Expandable title="details" defaultOpen={false}>
- **CI (review)** - issue page displays plan changes directly, no more context switching between tabs.
- **CD (deployment)** - rollout is now a standalone page, clearly separating review from execution.
- Rollout UI now supports release-based tasks — showing per-file execution status, command duration, and release info in task items.
- Rollout creation: introduce creation dependency between issue and rollout, with 2 rollout creation modes - 1) automatic creation, if issue is approved AND SQL review check pass; 2) manual creation, in other cases, e.g. issue approved BUT review not passed.
- Rollout creation: introduce creation dependency between issue and rollout, with 2 rollout creation modes - 1) automatic creation, if issue is approved AND SQL review check pass; 2) manual creation, in other cases, e.g. issue approved BUT review not passed. After rollout is created, issue status will be automatically set to `DONE`.
- Rollout permission: as a result of introducing manual creation, `bb.rollouts.create` permission is added to **Project Releaser** role . All custom roles for rollout initiation are advised to be assigned `bb.rollouts.create` permission (it only controls who can create a rollout, but it does not bypass approval requirements or task execution).
</Expandable>
- Remove `auto_resolve_issue` and `allow_modify_statement` from **Project Settings**.
- For Terraform, remove `allow_modify_statement` and `auto_resolve_issue` from the project resource, remove `auto_resolve_issue` from the workspace_profile setting resource.

Expand Down