name	update-dependencies
description	Updates dependencies in the PeerDB repository
disable-model-invocation	true

Make a to-do list for the following sequence, then execute it:

Make sure you're on the latest main branch. Run ./generate-protos.sh to avoid build failures down the line
Create a new branch update-dependencies (delete the old one if it's more than a few days old). Don't delete the remote branch
Update /nexus (Rust) a. cargo update b. see if cargo outdated -R has anything new (apart from prost that didn't resolve its compatibility issues after recent upstream changes, and tonic/tonic-health/pbjson/pbjson-types/reqwest it depends on, don't touch those). If it does, update those one by one in the right order and resolve incompatibilities, flagging to the user if something is non-trivial c. make sure the project builds with all features enabled (some are disabled by default)
Update /ui (TypeScript) a. npm update b. npm out, update the remaining ones one by on in the right order, resolve incompatibilities, flagging to the user if something is non-trivial c. test the build with npm run build d. run the linters from ui-lint.yml to validate
Update /flow (Go) a. go get -u . && go mod tidy - then undo the updates for dependencies marked as // PINNED, we have tasks for resolving those separately b. flag if anything else was breaking and doesn't have an easy fix c. validate with go build d. run the linters from golang-lint.yml e. run go run ./cmd/check_pinned_versions from flow/ to verify pinned versions are consistent
Update Buf plugins in buf.gen.yaml, flag if anything is more than a simple version bump
Report the summary to the user, listing all deps that needed a manual intervention. Prompt them to run the UI app locally to check for runtime errors. If there are unresolved Go dependency breaks, ask the user if they want to tackle them now or have you revert and mark as // PINNED. If downgrading: a. Carefully discover all related dependencies and restore the last working versions of them b. Add a // PINNED with a one-line explanantion to the dependency that broke c. Add a // PINNED to parent dependenices with a pointer to the root cause package d. Update the pinnedVersions map in flow/cmd/check_pinned_versions/main.go to match e. Outline an up to half-paragraph description of the hurdle to the user so they can put it in a task

name	update-dependencies
description	Updates dependencies in the PeerDB repository
disable-model-invocation	true

Make a to-do list for the following sequence, then execute it:

Make sure you're on the latest main branch. Run ./generate-protos.sh to avoid build failures down the line
Create a new branch update-dependencies (delete the old one if it's more than a few days old). Don't delete the remote branch
Update /nexus (Rust) a. cargo update b. see if cargo outdated -R has anything new (apart from prost that didn't resolve its compatibility issues after recent upstream changes, and tonic/tonic-health/pbjson/pbjson-types/reqwest it depends on, don't touch those). If it does, update those one by one in the right order and resolve incompatibilities, flagging to the user if something is non-trivial c. make sure the project builds with all features enabled (some are disabled by default)
Update /ui (TypeScript) a. npm update b. npm out, update the remaining ones one by on in the right order, resolve incompatibilities, flagging to the user if something is non-trivial c. test the build with npm run build d. run the linters from ui-lint.yml to validate
Update /flow (Go) a. go get -u . && go mod tidy - then undo the updates for dependencies marked as // PINNED, we have tasks for resolving those separately b. flag if anything else was breaking and doesn't have an easy fix c. validate with go build d. run the linters from golang-lint.yml e. run go run ./cmd/check_pinned_versions from flow/ to verify pinned versions are consistent
Update Buf plugins in buf.gen.yaml, flag if anything is more than a simple version bump
Report the summary to the user, listing all deps that needed a manual intervention. Prompt them to run the UI app locally to check for runtime errors. If there are unresolved Go dependency breaks, ask the user if they want to tackle them now or have you revert and mark as // PINNED. If downgrading: a. Carefully discover all related dependencies and restore the last working versions of them b. Add a // PINNED with a one-line explanantion to the dependency that broke c. Add a // PINNED to parent dependenices with a pointer to the root cause package d. Update the pinnedVersions map in flow/cmd/check_pinned_versions/main.go to match e. Outline an up to half-paragraph description of the hurdle to the user so they can put it in a task

update-dependencies

المزيد من هذا المستودع

المزيد من هذا المستودع