# What's the best way to fix a metadata commit that has errors?

**URL:** <https://discourse.julialang.org/t/whats-the-best-way-to-fix-a-metadata-commit-that-has-errors/8893>\
**Category:** Internals & Design\
**Tags:** question, package\
**Created:** [February 7, 2018, 12:58pm UTC](https://discourse.julialang.org/t/whats-the-best-way-to-fix-a-metadata-commit-that-has-errors/8893 "2018-02-07T12:58:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xiaodai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xiaodai/32/15937_2.png) [@xiaodai](https://discourse.julialang.org/u/xiaodai)\
**Post date:** [February 7, 2018, 12:58pm UTC](https://discourse.julialang.org/t/whats-the-best-way-to-fix-a-metadata-commit-that-has-errors/8893/1 "2018-02-07T12:58:41Z")

</div>

I am developing some packages but then I run into issues where I tag a released and JuliaCIBot runs into an error because one of packages I had used in runtests.jl is not in REQUIRE.

In that case, once I have fixed the code, do I need to tag a new release as bug fix? Or it can piggy-back on the merge?

My specific issue was that I had a `using BenchmarkTools` in my runtests.jl, which wasn’t needed. So I just wanted to remove that line, but feel that tagging a new release seems wasteful.

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [February 7, 2018, 1:16pm UTC](https://discourse.julialang.org/t/whats-the-best-way-to-fix-a-metadata-commit-that-has-errors/8893/2 "2018-02-07T13:16:49Z")

</div>

You shouldn’t change the identity of an existing version so tagging a new one seems like the easiest way forward.