From c6f97f7f925fe7846e96f9b376a0556056ef7a09 Mon Sep 17 00:00:00 2001 From: Abdullah Yildirim Date: Tue, 12 Mar 2024 11:23:30 -0400 Subject: [PATCH] Update development.md Co-authored-by: Keran Yang Signed-off-by: a3hadi --- development.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/development.md b/development.md index bdb128d9..90a5af82 100644 --- a/development.md +++ b/development.md @@ -31,7 +31,7 @@ This is essentially equivalent to running `make image-push TAG=` in the exa 1. Create a PR for your changes. Once merged, it will trigger a workflow to build and push the images for all the examples, with the tag `stable`. This consistent tag name is used so that the tags in the [E2E test pipelines](https://github.com/numaproj/numaflow/tree/main/test) do not need to be updated each time a new change is made. -2. If the change that you have introduced is a breaking change, i.e. adds new features/logic, then after merge it is encouraged to update the dependency management files so that the version +2. If the change that you have introduced is a breaking change, then after merge you should update the dependency management files so that the version displayed in the `go.mod` file reflects the commit SHA of the merged changes. This can be done by getting the commit SHA of the merged changes and using it with the update script. Alternatively, you can provide the specific version that you would like to update to, or even pass in `latest` to fetch the latest version from the remote repository: