bea0433b54
* Fix the release process's latest step The automated release of 0.36.0 was attempted last night but it failed due to a [failure on CI][bad]. This failure comes about because it was trying to change the release date of 0.35.0 which ended up not modifying any fails so `git` failed to commit as no files were changed. The original bug though was that 0.35.0 was being changed instead of 0.36.0. The reason for this is that the script used `--sort=-committerdate` to determine the latest branch. I forgot, though, that with backports it's possible for 0.35.0 to have a more recent commit date than 0.36.0 (as is currently the case). This commit updates the script to perform a numerical sort outside of git to get the latest release branch. Additionally this adds in some `set -ex` commands for the shell which should help print out commands as they're run and assist in future debugging. [bad]: https://github.com/bytecodealliance/wasmtime/runs/6087188708 * Replace sed with rust
19 lines
593 B
Rust
19 lines
593 B
Rust
fn main() {
|
|
let date = std::env::args().nth(1).unwrap();
|
|
let relnotes = std::fs::read_to_string("RELEASES.md").unwrap();
|
|
let mut new_relnotes = String::new();
|
|
let mut counter = 0;
|
|
for line in relnotes.lines() {
|
|
if line.starts_with("Unreleased") {
|
|
counter += 1;
|
|
if counter == 2 {
|
|
new_relnotes.push_str(&format!("Released {}\n", date));
|
|
continue;
|
|
}
|
|
}
|
|
new_relnotes.push_str(line);
|
|
new_relnotes.push_str("\n");
|
|
}
|
|
std::fs::write("RELEASES.md", new_relnotes).unwrap();
|
|
}
|