The artefact is also present for me. It's being tracked on the GitHub Issue Tracker.
Thanks! This should now be fixed in the latest build.
