From dfd4345a59f601e3906a9ff131a910f7fd8fa8f8 Mon Sep 17 00:00:00 2001 From: Kenneth Bingham Date: Tue, 26 Sep 2023 11:17:54 -0400 Subject: [PATCH] clarify adjacent working copies for changed modules are required --- RELEASING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASING.md b/RELEASING.md index 6c287a8b0..1cc119392 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -36,7 +36,7 @@ Perform these steps in PR branches based on release-next (trunk). 1. Make sure you have a clean build in GitHub Actions. 2. Make sure you have a clean build in fablab smoketest. 5. Ensure CHANGELOG.md is up to date. - 1. Run `ziti-ci build-release-notes` in your PR branch to generate library version updates and summarize issues + 1. Run `ziti-ci build-release-notes` in your PR branch to generate library version updates and summarize issues. Note that you will need a working copy of each module that has changed in an adjacent directory with the default repo name in order for this to work. fixed, as long as the git commit has `fixed #` (or fixes, closes, closed, etc.). 1. Sanity-check and paste the output into CHANGELOG.md under a heading like `## Component Updates and Bug Fixes`.