@@ -152,36 +152,8 @@ make toolchain-shell
152152make toolchain-update
153153```
154154
155-
156- ### Release Process
157-
158- 0 . Determine the release semver version by consulting the [ changelog] ( ./CHANGELOG.MD ) .
159- 1 . Create a branch for your release e.g.
160- ` git checkout -b release/v1.0.0 `
161- 2 . Run ` make dist ` as described in [ "Release" section] ( #release )
162- 3 . Commit the new dist folder ` git commit -m "Release v1.0.0" -- dist/ `
163- 4 . Push up your branch to github, and make a pull request.
164- 5 . You may also create and push a signed ` -rcX ` git tag where the number after ` rc ` doesn't already exist.
165- ` git tag -S v1.0.0-rc0 -m v1.0.0-rc0 `
166- ` git push origin v1.0.0-rc0 `
167- 6 . Wait for others to replicate your build, see [ "Verify" section] ( #verify )
168- 7 . Once the release has enough ` git sig ` signatures, make the final tag and merge the pull request.
169- ` git tag -S v1.0.0 -m v1.0.0 `
170- ` git push origin v1.0.0 `
171-
172-
173155[ gs ] : https://codeberg.org/distrust/git-sig
174156
175- ### LFS setup
176-
177- This repository externalises large files so that they do not bulk up the git repo itself.
178- This is done through a tool called ` git-lfs ` , which must be installed for it to work.
179- Additionally, we use a custom agent to store our LFS objects in S3 (rather than the default and more expensive Github LFS service).
180-
181- In order to setup our s3 based lfs:
182-
183- 1 ) Install [ tkinfra] ( https://github.com/tkhq/mono/tree/main/src/go/tkinfra )
184- 2 ) Run ` ./scripts/setup-lfs.sh `
185157
186158#### Troubleshooting
187159
0 commit comments