Tags: linebender/xilem
Tags
Release Xilem/Masonry v0.4.0, Tree Arena v0.2.0 (#1435) See discussion in [#xilem > v0.4.0](https://xi.zulipchat.com/#narrow/channel/354396-xilem/topic/v0.2E4.2E0/with/547457987). Target date is tomorrow to just let everything settle (e.g. #1103). https://linebender.org/wiki/process/release/#checklist I have run a publish dry run, using the command: ```sh cargo publish --dry-run -p xilem -p xilem_core -p masonry -p masonry_core -p masonry_winit -p masonry_testing -p tree_arena -p xilem_web ``` We don't have a changelog (yet, plan is to start immediately after this releasee), we have bumped dependencies (pending #1103).
Release Xilem/Masonry v0.4.0, Tree Arena v0.2.0 (#1435) See discussion in [#xilem > v0.4.0](https://xi.zulipchat.com/#narrow/channel/354396-xilem/topic/v0.2E4.2E0/with/547457987). Target date is tomorrow to just let everything settle (e.g. #1103). https://linebender.org/wiki/process/release/#checklist I have run a publish dry run, using the command: ```sh cargo publish --dry-run -p xilem -p xilem_core -p masonry -p masonry_core -p masonry_winit -p masonry_testing -p tree_arena -p xilem_web ``` We don't have a changelog (yet, plan is to start immediately after this releasee), we have bumped dependencies (pending #1103).
Remove 6th keyword from `xilem_web`. (#976) Apparently 5 is the maximum. ``` error: failed to publish to registry at https://crates.io Caused by: the remote server responded with an error (status 400 Bad Request): expected at most 5 keywords per crate ```
Prepare to release 0.3.0. (#973) We skip Xilem 0.2.0 and go straight to 0.3.0 in order to synchronize the version with its companion packages that are expected to be updated in lock-step for now. [The one exception is `tree_arena`](https://xi.zulipchat.com/#narrow/channel/419691-linebender/topic/Xilem.20version.20sync/with/517174026), which will retain its own version pacing, because it's likely to see fewer updates.
Implement underlining for IME areas (#284) 