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: README.md
+16-21Lines changed: 16 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,48 +113,43 @@ All SDKs version on the same cadence. To publish a new version (of all SDKs), fo
113
113
114
114
1. Update the `VERSION_FROM` and `VERSION_TO` values in the `release:all` task in [`./project.json`](./project.json).
115
115
116
-
1. Leaving that single change uncommitted, make sure you've exported a GitHub access token (as `GITHUB_TOKEN` -- see below) with push access to `main` branch of the repository, then run the release script:
116
+
1. Leaving that single change uncommitted and run the release script:
117
117
118
118
```bash
119
-
npm run release
119
+
npm run release:create-branch
120
120
```
121
121
122
122
This script:
123
123
124
124
- Updates the version numbers in all affected files
125
125
- Rebuilds all SDKs
126
126
- Commits all changes (e.g., to version files, lockfiles, and anything else under `./sdk`)
127
-
- Adds two new tags to mark the release (`v0.0.0` and `sdk/go/v0.0.0`)
128
-
- Pushes the commit and tags to GitHub, triggering the `publish` task
129
-
- Creates a new GitHub release
127
+
- Pushes the branch to GitHub
130
128
131
-
If for some reason the Buildkite publish job doesn't finish successfully, you can run some or all publish tasks from your local machine by exporting the applicable environment variables (again, see below), then running:
129
+
1. Next open a PR with the created branch.
130
+
131
+
1. After the PR is merged, from an up-to-date main branch, create and push the release tags:
132
132
133
133
```bash
134
-
npm run clean
135
-
npm run build
136
-
npm run publish # To publish all packages
137
-
npx nx publish sdk/typescript # To publish only the Node.js package
138
-
npx nx publish sdk/python # To publish only the Python package
139
-
npx nx publish sdk/go # To publish only the Go package
140
-
npx nx publish sdk/ruby # To publish only the Ruby package
134
+
git tag v{VERSION_TO} main
135
+
git tag sdk/go/v{VERSION_TO} main
136
+
137
+
git push origin v{VERSION_TO}
138
+
git push origin sdk/go/v{VERSION_TO}
141
139
```
142
140
143
-
1. Once the `publish` job completes, verify the releases at their respective URLs:
141
+
1. Once the tags have been created, manually trigger the SDK Release Pipeline in Buildkite. After the pipeline has finished, manually create a release in GitHub ([example](https://github.com/buildkite/buildkite-sdk/releases/tag/v0.5.0)).
0 commit comments