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
Copy file name to clipboardExpand all lines: RELEASING.md
+15-7Lines changed: 15 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,14 +123,22 @@ The `pre-release-all` or `pre-release` command must be run first:
123
123
- Handles prerelease numbering with leading zeros
124
124
- Writes the next version to a file in the build directory, located at `.github/scripts/.build/<module>-next-tag`
125
125
126
-
### 2. Pre-Release Check
127
-
The `release-all` command automatically runs `check-pre-release` for all modules to verify:
128
-
- The `.github/scripts/.build` directory exists
129
-
- Each module has a corresponding `<module>-next-tag` file
130
-
- The version in the `<module>-next-tag` file matches the version in `<module>/version.go`
126
+
### 2. Release Validation Checks
127
+
Before creating any commits or tags, the release script performs the following validation checks:
128
+
129
+
**Git Remote Validation:**
130
+
- Verifies that the `origin` remote points to `git@github.com:docker/go-sdk.git` (or HTTPS equivalent)
131
+
- Prevents accidentally pushing releases to forks or personal repositories
132
+
- If validation fails, the script aborts immediately with instructions to fix the remote
133
+
134
+
**Pre-Release Verification:**
135
+
- The `release-all` command automatically runs `check-pre-release` for all modules
136
+
- Verifies the `.github/scripts/.build` directory exists
137
+
- Checks each module has a corresponding `<module>-next-tag` file
138
+
- Validates the version in `<module>-next-tag` matches the version in `<module>/version.go`
131
139
- If any checks fail, the release is aborted with an error message
132
-
133
-
This check is implemented in `.github/scripts/check-pre-release.sh` and ensures that `pre-release-all` was completed successfully (with `DRY_RUN=false`) and that all version files are properly updated before proceeding with the release.
140
+
- Implemented in `.github/scripts/check-pre-release.sh`
141
+
- Ensures `pre-release-all` was completed successfully (with `DRY_RUN=false`)
134
142
135
143
You can manually run the check for a specific module:
0 commit comments