You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> We need to publish a new tag for a new version, the tag must be a valid [Semantic Version](https://semver.org/)**preceded with a v (for example, v1.2.3)**. There must not be a branch name with the same name as the tag.
78
78
79
79
1. Develop and merge the feature code.
80
-
2. Create a new PR to update the version in [`./VERSION`](./VERSION)
81
-
3. After the version is updated, the action [`./.github/workflows/release.yml`](./.github/workflows/release.yml) will use the newest version `x.y.z` to create a new tag `vx.y.z`, then use the tag to create the release.
80
+
1. Create a new PR to update the version in [`./VERSION`](./VERSION)
81
+
1. After the version is updated, the action [`./.github/workflows/release.yml`](./.github/workflows/release.yml) will use the newest version `x.y.z` to create a new tag `vx.y.z`, then use the tag to create the release.
Copy file name to clipboardExpand all lines: examples/setup/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,5 +6,5 @@ We will create two environments named `dev` and `prod`. Each environment contain
6
6
Before you start, please make sure you have running your Bytebase service and have created the service account, and replace the provider initial variables. Check the [README](../README.md) for details.
0 commit comments