[WARN ] Crates.io index doesn't exist. Consider using --update-crates-index to help determining if release versions are published already
[INFO ] WOULD auto-bump provided package 'a' from 0.8.0 to 0.9.0 for publishing
[INFO ] WOULD adjust 1 manifest version due to breaking change in 'a': 'b' 0.8.0 ➡ 0.9.0
[INFO ] WOULD adjust 1 manifest version due to breaking change in 'b': 'c' 8.0.0 ➡ 9.0.0
[INFO ] WOULD modify existing changelog for 'a'.
[TRACE] Pending 'a' manifest version update: "0.9.0"
[TRACE] Pending 'b' manifest version update: "0.9.0"
[TRACE] Pending 'b' manifest dependencies update: 'a = "^0.9.0"' (from  "0.8.0" )
[TRACE] Pending 'c' manifest version update: "9.0.0"
[TRACE] Pending 'c' manifest dependencies update: 'b = "^0.9.0"' (from  "0.8.0" )
[TRACE] WOULD persist changes to 3 manifests and 1 changelogs with: "Adjusting changelogs prior to release of a v0.9.0, safety bump 2 crates\n\nSAFETY BUMP: b v0.9.0, c v9.0.0"
[INFO ] Up to 1 changelog would be previewed if the --execute is set and --no-changelog-preview is unset.
[WARN ] This changelog is likely to be fully generated from commit history or contain lower-case git-conventional headlines: a
[TRACE] WOULD run "git" "commit" "-am" "Adjusting changelogs prior to release of a v0.9.0, safety bump 2 crates\n\nSAFETY BUMP: b v0.9.0, c v9.0.0"
[TRACE] WOULD create tag object a-v0.9.0 with changelog message, first line is: '### refactor (BREAKING)'
[TRACE] WOULD run "gh" "release" "create" "a-v0.9.0" "--title" "a v0.9.0" "--notes" "### refactor (BREAKING…" [note truncated]