# Using JuliaRegistrator: difficulty registering new releases

**URL:** <https://discourse.julialang.org/t/using-juliaregistrator-difficulty-registering-new-releases/42178>\
**Category:** General Usage\
**Tags:** question, package\
**Created:** [June 28, 2020, 1:20am UTC](https://discourse.julialang.org/t/using-juliaregistrator-difficulty-registering-new-releases/42178 "2020-06-28T01:20:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![fusion809](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fusion809/32/6080_2.png) [@fusion809](https://discourse.julialang.org/u/fusion809)\
**Post date:** [June 28, 2020, 1:20am UTC](https://discourse.julialang.org/t/using-juliaregistrator-difficulty-registering-new-releases/42178/1 "2020-06-28T01:20:25Z")

</div>

My FunctionIntegrator.jl package is now officially in the General registry and I’m having a little difficulty with getting JuliaRegistrator to register a new release of my package. I created a comment on the commit tagged as v0.2.0 that was just:

```markdown
@JuliaRegistrator register

```

and I received the following error from JuliaRegistrator:

```markdown
Error while trying to register: "Tag with name v0.2.0 already exists and points to a different commit"

```

. This error is not completely unexpected as the v0.2.0 tag _used_ to point to a different commit, but the commit I added this comment to is for the new v0.2.0 tagged commit. The only reason I changed the tagged commit was because in the old commit tagged as v0.2.0 (which was several commits ago) I forgot to update the Project.toml file accordingly and JuliaRegistrator complained about this when I tried to register that tag. Is there a way to get around this error?

Thanks for your time and patience.

---

<div class="post-metadata">

**Author:** ![mbaz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbaz/32/17295_2.png) [@mbaz](https://discourse.julialang.org/u/mbaz)\
**Post date:** [June 28, 2020, 1:27am UTC](https://discourse.julialang.org/t/using-juliaregistrator-difficulty-registering-new-releases/42178/2 "2020-06-28T01:27:34Z")

</div>

In my experience, the version specified in Project.toml must not exist as a tag when you register a new version. The workflow is to add the tag after the registration/update is successful (merged).

---

<div class="post-metadata">

**Author:** ![fusion809](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fusion809/32/6080_2.png) [@fusion809](https://discourse.julialang.org/u/fusion809)\
**Post date:** [June 28, 2020, 1:30am UTC](https://discourse.julialang.org/t/using-juliaregistrator-difficulty-registering-new-releases/42178/3 "2020-06-28T01:30:39Z")

</div>

> [@mbaz](#):
>
> cified in Project.toml must not exist as a tag when you register a new version. The workflow is to add the tag after the registration/update is successful (merged).

Ah, deleting it fixed this, thanks!

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [June 28, 2020, 2:01am UTC](https://discourse.julialang.org/t/using-juliaregistrator-difficulty-registering-new-releases/42178/4 "2020-06-28T02:01:09Z")

</div>

If you use TagBot you don’t have to manually tag new versions: [https://github.com/marketplace/actions/julia-tagbot](https://github.com/marketplace/actions/julia-tagbot)