d57c78bc71
This is how I did it: 1. `git clone https://github.com/ooni/probe-engine internal/engine` 2. ``` (cd internal/engine && git describe --tags) v0.23.0 ``` 3. `nvim go.mod` (merging `go.mod` with `internal/engine/go.mod` 4. `rm -rf internal/.git internal/engine/go.{mod,sum}` 5. `git add internal/engine` 6. `find . -type f -name \*.go -exec sed -i 's@/ooni/probe-engine@/ooni/probe-cli/v3/internal/engine@g' {} \;` 7. `go build ./...` (passes) 8. `go test -race ./...` (temporary failure on RiseupVPN) 9. `go mod tidy` 10. this commit message Once this piece of work is done, we can build a new version of `ooniprobe` that is using `internal/engine` directly. We need to do more work to ensure all the other functionality in `probe-engine` (e.g. making mobile packages) are still WAI. Part of https://github.com/ooni/probe/issues/1335
1.0 KiB
1.0 KiB
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Routine sprint releases | Bi-weekly releases of probe-engine, etc. | effort/M, priority/medium | bassosimone |
- psiphon: run ./update.bash
- engine: update dependencies
- engine: update internal/httpheader/useragent.go
- engine: update version/version.go
- engine: update resources/assets.go
- engine: update bundled certs (using
go generate ./...) - engine: make sure all workflows are green
- engine: tag a new version
- engine: update again version.go to be alpha
- engine: create release at GitHub
- engine: update mobile-staging branch to create oonimkall
- cli: pin to latest engine
- cli: update internal/version/version.go
- cli: tag a new version
- cli: update internal/version/version.go again to be alpha
- android: pin to latest oonimkall
- ios: pin to latest oonimkall
- desktop: pin to latest cli
- engine: create issue for next routine release
- e2etesting: see whether we can remove legacy checks