Repository: zng-ui/zng (language: rust)

Issue:
Version 0.10 and early has duplicate dependencies
`zng = "0.10"` gets two conflicting `zng-var` and other crate dependencies.

Version 0.10 and early does not build anymore anyway because of external deps breaking (swgl and others), but we need to understand how it happened, the publish script should always keep everything in sync.


Discussion / hints:
In the [0.11 release ](https://github.com/zng-ui/zng/pull/392/files#diff-62f838e82bcd279049a23e53661cf15babf17b9cf05f56f50600d808d9e03691L88) `zng-app` starts depending on the new `zng-var@0.5`, but only bumps patch, **this is an error**  because the var types are used in the public API for `zng-app`.

Fix patch:
diff --git a/docs/release-process.md b/docs/release-process.md
index 17540cfaa..905eb4b15 100644
--- a/docs/release-process.md
+++ b/docs/release-process.md
@@ -14,6 +14,8 @@ To make a release a `zng-ui` project owner needs to follow/monitor these steps:
     * This includes `Cargo.toml` version changes that must be reviewed manually.
     * You can use `do publish --diff` to get a list of crates and files that changed.
     * You can use `cargo semver-checks` to find breaking changes.
+        - **Warning** This tool does not find all breaking changes, specially it does not detect usage
+          of dependency types in the public API when that dependency was upgraded.
     * You can use `do publish --bump` to set the versions, update Cargo.toml doc examples and close the changelog.
     * Note that if setting manually the `zng-view-prebuilt` needs to have the same version as `zng`.
 
@@ -28,6 +30,11 @@ To make a release a `zng-ui` project owner needs to follow/monitor these steps:
     * If GitHub release and docs update:
         - It will publish to crates.io using `do publish --execute`.
 
+4. Test previous breaking version.
+   * Make a test crate that depends on the previous minor version of `zng`.
+   * If it does not build a breaking change in the public API was introduced.
+   * Unfortunately there is no "staging" for publish so you might need to yank all the affected crates.
+
 ## Webrender
 
 Webrender is not published so we maintain our own fork in <https://github.com/zng-ui/zng-webrender>. These crates mostly untouched,


Test patch: