New version: MeshCat v0.9.0

[JuliaRegistrator]

• Registering package: MeshCat
• Repository: https://github.com/rdeits/MeshCat.jl
• Created by: @tkoolen
• Version: v0.9.0
• Commit: 89ecad28a36d8017c8301c0605d8565a0508782e
• Reviewed by: @tkoolen
• Reference: rdeits/MeshCat.jl@89ecad2#commitcomment-36596154
• Release notes:

• Add missing kwargs propagation in arrow_visualizer.jl Adds missing kwargs propagation in arrow_visualizer.jl rdeits/MeshCat.jl#130 (thanks, @ferrolho)
• Update meshcat to meshcat-dev/meshcat@ae82a61.
• Use FFMPEG.jl to provide ffmpeg binary (Update meshcat rdeits/MeshCat.jl#131)
• Add Blink.jl as a dependency to work around Pkg resolver issues (Register MolecularGraph: 0.3.0 #135).

[github-actions]

Your new version pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: BinDeps, Colors, CoordinateTransformations, DocStringExtensions, FFMPEG, Parameters, Requires, Rotations, StaticArrays. You may find CompatHelper helpful for keeping your compat entries up-to-date.

Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versionsyour package is compatible with. See [https://julialang.github.io/Pkg.jl/v1/compatibility/.] for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[github-actions]

Your new version pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: BinDeps, Colors, CoordinateTransformations, DocStringExtensions, FFMPEG, Parameters, Requires, Rotations, StaticArrays. You may find CompatHelper helpful for keeping your compat entries up-to-date.Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versions your package is compatible with. See https://julialang.github.io/Pkg.jl/v1/compatibility/ for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[tkoolen]

Please don't merge this. We plan to tighten the bounds and just rely on auto-merge from now on.

[github-actions]

Your new version pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: BinDeps, Colors, CoordinateTransformations, DocStringExtensions, FFMPEG, Parameters, Requires, Rotations, StaticArrays. You may find CompatHelper helpful for keeping your compat entries up-to-date.Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versions your package is compatible with. See https://julialang.github.io/Pkg.jl/v1/compatibility/ for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[DilumAluthge]

Please don't merge this. We plan to tighten the bounds and just rely on auto-merge from now on.

Okay, I’ll close this PR. You can make a new registration when you are ready.