Added information for new --with-unpublished-dependencies flag (Myste…

…nLabs#7635)

doc/src/build/cli-client.md

@@ -582,6 +582,8 @@ The `--verify-dependencies` flag can fail the publish for other reasons, as well
 * The address supplied for the dependency points to an object instead of a package.
 * The CLI fails to connect to the node to fetch the package.
 
+**Note:** If your package includes unpublished depenedencies, you can add the `--with-unpublished-dependencies` flag to the `sui client publish` command to include modules from those packages in the published build.
+
 If successful, your response resembles the following:
 
 ```shell

doc/src/build/json-rpc.md

@@ -165,7 +165,7 @@ sure the package is valid. If some modules have [initializers](move/debug-publis
 To publish a Move module, you also need to include `{{vector_of_compiled_modules}}`. To generate the value of this field, use the `sui move` command. The `sui move` command supports printing the bytecode as base64:
 
 ```
-sui move <move-module-path> build --dump-bytecode-as-base64
+sui move <move-module-path> build --dump-bytecode-as-base64 
 ```
 
 Assuming that the location of the package's sources is in the `PATH_TO_PACKAGE` environment variable an example command resembles the following:
@@ -181,3 +181,5 @@ Copy the output base64 representation of the compiled Move module into the
 REST publish endpoint.
 
 The command generates a package object that represents the published Move code. You can use the package ID as an argument for subsequent Move calls to functions defined in this package.
+
+**Note:** If your package has dependencies that are unpublished, include the `--with-unpublished-dependencies` flag to have the modules in those packages added to the bytecode.