-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ooniprobe-cli v3.22 release process #2722
Labels
Comments
This was referenced May 13, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 13, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 13, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 13, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 13, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 13, 2024
I have used gomajor and upgraded what I could. It still seems impossible to upgrade snowflake because there is the issue of the shared refraction-networking/utls dependency. See ooni/probe#2722
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 13, 2024
I've used both `gomajor` and `go get -u -v ./...` to update all the dependencies I could. It still feels impossible to upgrade snowflake because of the incompatible dependency with Psiphon (I previously described this issue at refraction-networking/utls#249 and there has been some very useful and much appreciated follow-up discussion at refraction-networking/utls#290, which possibly will lead to solving the whole issue, which is contingent to current uTLS versions used by Psiphon and Snowflake, in a systemic and more fundamental way). Part of ooni/probe#2722.
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 13, 2024
bassosimone
added a commit
to ooni/probe-assets
that referenced
this issue
May 13, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 13, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 13, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 14, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 14, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 14, 2024
This was referenced May 14, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 14, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 14, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 14, 2024
With this change, we finish addressing all the `gosec` warnings that, on paper, looked relatively easy to fix. The remaining warnings need more thinking to be either dismissed or addressed properly. Part of ooni/probe#2722
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 15, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 15, 2024
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 17, 2024
I manually tested the cli and concluded that it's too easy to reach the panic caused by runtimex.Try0 over there and it would expose panics to users too frequently. Let's just convert those into normal error checks. Here is what we would previously get: ``` % ./ooniprobe rm ? Are you sure you wish to delete the result #0 [Use arrows to move, type to filter] true > false panic: Try0: interrupt [...] ``` So, here I just pressed ^D and got a panic. Ouch! After the diff, we have this: ``` % ./ooniprobe rm ? Are you sure you wish to delete the result #0 false ⨯ failure in main command error=canceled by user ``` and: ``` % ./ooniprobe rm --all ? Are you sure you wish to delete ALL results false ⨯ failure in main command error=canceled by user ``` It seems much better, isn't it? Part of the QA for ooni/probe#2722
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 17, 2024
I manually tested the cli and concluded that it's too easy to reach the panic caused by runtimex.Try0 over there and it would expose panics to users too frequently. Let's just convert those into normal error checks. Here is what we would previously get: ``` % ./ooniprobe rm ? Are you sure you wish to delete the result #0 [Use arrows to move, type to filter] true > false panic: Try0: interrupt [...] ``` So, here I just pressed ^D and got a panic. Ouch! After the diff, we have this: ``` % ./ooniprobe rm ? Are you sure you wish to delete the result #0 false ⨯ failure in main command error=canceled by user ``` and: ``` % ./ooniprobe rm --all ? Are you sure you wish to delete ALL results false ⨯ failure in main command error=canceled by user ``` It seems much better, isn't it? Part of the QA for ooni/probe#2722
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 17, 2024
I manually tested the cli and concluded that it's too easy to reach the panic caused by runtimex.Try0 over there and it would expose panics to users too frequently. Let's just convert those into normal error checks. Here is what we would previously get: ``` % ./ooniprobe rm ? Are you sure you wish to delete the result #0 [Use arrows to move, type to filter] true > false panic: Try0: interrupt [...] ``` So, here I just pressed ^D and got a panic. Ouch! After the diff, we have this: ``` % ./ooniprobe rm ? Are you sure you wish to delete the result #0 false ⨯ failure in main command error=canceled by user ``` and: ``` % ./ooniprobe rm --all ? Are you sure you wish to delete ALL results false ⨯ failure in main command error=canceled by user ``` It seems much better, isn't it? Part of the QA for ooni/probe#2722
bassosimone
added a commit
to ooni/probe-engine
that referenced
this issue
May 20, 2024
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Release information
Fill out this information for each release:
Version Number: 3.22.0
Expected Release date: May 22, 2023
Summary of changes:
Link to latest nightly: https://github.com/ooni/probe-cli/releases/tag/rolling
Pre-release communication
Release checklist
For extended documentation about the process, see probe-cli's releasing.md.
Psiphon
./script/go.bash get -u -v
: already there, no changes needed./script/go.bash list -json ./cmd/ooniprobe
does not include any pinned package in psiphon'sgo.mod
or otherwise ask Psiphon developers whether this is fine: same as before, so we should be fineGo version
.github/workflows/gobash.yml
: not neededGOVERSION
file if needed: chore: update to go1.21.10 probe-cli#1596toolchain
line inside ofgo.mod
: chore: update to go1.21.10 probe-cli#1596Readme.md
file: chore: update to go1.21.10 probe-cli#1596Android
NDKVERSION
, andMOBILE/android/ensure
if needed: chore(NDKVERSION): upgrade to latest LTS release probe-cli#1597Dependencies other than Psiphon
./script/go.bash get -u -v -d ./...
: chore: upgrade most dependencies probe-cli#1598Updating assets and definitions
./script/updateminipipeline.bash
: chore: upgrade assets and definitions probe-cli#1600./script/go.bash generate ./...
): chore: upgrade assets and definitions probe-cli#1600internal/model/http.go
: chore: upgrade assets and definitions probe-cli#1600Maintenance
./internal/stuninput
): chore: minor changes before alpha release probe-cli#1601QA and alpha releasing
gosec
runs: chore: start addressing gosec warnings probe-cli#1602 chore: continue to address gosec warnings probe-cli#1604 chore: address additional gosec warnings probe-cli#1605 chore: finish addressing ~easy gosec warnings probe-cli#1603./script/go.bash test -race -count 1 ./...
must pass locallyReleasing proper
internal/version/version.go
in release/X.Y to be a stable releasePublishing stable packages
./script/autoexport.bash
: https://github.com/ooni/probe-engine/releases/tag/v0.29.0Post-release communication
#ooni-probe-releases
slack channel:The text was updated successfully, but these errors were encountered: