mirror of
				https://github.com/BurntSushi/ripgrep.git
				synced 2025-10-30 23:17:47 +02:00 
			
		
		
		
	doc: move CHANGELOG update before dependency updates
It seems better to write this first. Especially so it gets included into crate publishes.
This commit is contained in:
		| @@ -7,6 +7,7 @@ | ||||
|   a strong motivation otherwise, review and update every dependency. Also | ||||
|   run `--aggressive`, but don't update to crates that are still in beta. | ||||
| * Update date in `crates/core/flags/doc/template.rg.1`. | ||||
| * Update the CHANGELOG as appropriate. | ||||
| * Review changes for every crate in `crates` since the last ripgrep release. | ||||
|   If the set of changes is non-empty, issue a new release for that crate. Check | ||||
|   crates in the following order. After updating a crate, ensure minimal | ||||
| @@ -22,7 +23,6 @@ | ||||
|     * crates/printer | ||||
|     * crates/grep (bump minimal versions as necessary) | ||||
|     * crates/core (do **not** bump version, but update dependencies as needed) | ||||
| * Update the CHANGELOG as appropriate. | ||||
| * Edit the `Cargo.toml` to set the new ripgrep version. Run | ||||
|   `cargo update -p ripgrep` so that the `Cargo.lock` is updated. Commit the | ||||
|   changes and create a new signed tag. Alternatively, use | ||||
|   | ||||
		Reference in New Issue
	
	Block a user