Add changelog entries

packages/scripts/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## Unreleased
 
+### Enhancements
+
+-   Recommend listing JavaScript entry points as paths passed to the `start` and `build` commands ([#68251](https://github.com/WordPress/gutenberg/pull/68251)).
+-   Introduce a new option `--source-path` to customize the source directory used with the `start` and `build` commands ([#68251](https://github.com/WordPress/gutenberg/pull/68251)).
+
 ## 30.7.0 (2024-12-11)
 
 ### Internal

packages/scripts/README.md

@@ -622,15 +622,17 @@ The `build` and `start` commands use [webpack](https://webpack.js.org/) behind t
 
 ### Listing entry points
 
-The simplest way to list JavaScript entry points is to pass them as arguments for the command:
+The simplest way to list JavaScript entry points is to pass them as arguments for the command.
+
+_Example:_
 
 ```bash
 wp-scripts build entry-one.js entry-two.js
 ```
 
 ### Automatic block.json detection and the source code directory
 
-A convenient alternative for blocks is using automatic entry points detection. In that case, the source code directory (the default is `./src`) and its subdirectories are scanned for the existence of `block.json` files. If one or more are found, the JavaScript files listed in metadata are treated as entry points and will be output into corresponding folders in the `build` directory. The script fields in `block.json` should pass relative paths to `block.json` in the same folder.
+A convenient alternative for blocks is using automatic entry point detection. In that case, the source code directory (the default is `./src`) and its subdirectories are scanned for the existence of `block.json` files. If one or more are found, the JavaScript files listed in metadata are treated as entry points and will be output into corresponding folders in the `build` directory. The script fields in `block.json` should pass relative paths to `block.json` in the same folder.
 
 _Example:_