# \`TagBot\`: release for new version not automatically triggered

**URL:** <https://discourse.julialang.org/t/tagbot-release-for-new-version-not-automatically-triggered/95179>\
**Category:** Package Management\
**Tags:** question, package, tagbot\
**Created:** [February 25, 2023, 10:03am UTC](https://discourse.julialang.org/t/tagbot-release-for-new-version-not-automatically-triggered/95179 "2023-02-25T10:03:54Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![pat-alt](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pat-alt/32/34264_2.png) [@pat-alt](https://discourse.julialang.org/u/pat-alt)\
**Post date:** [February 25, 2023, 10:03am UTC](https://discourse.julialang.org/t/tagbot-release-for-new-version-not-automatically-triggered/95179/1 "2023-02-25T10:03:54Z")

</div>

Hi there,

I recently moved various packages from my own GitHub account into a new [organisation](https://github.com/JuliaTrustworthyAI). Yesterday, I added a new release for one of them to General and as usual TagBot was triggered (see [here](https://github.com/JuliaTrustworthyAI/CounterfactualExplanations.jl/issues/22#issuecomment-1444629391)). I can also see that a new tag has been automatically created [here](https://github.com/JuliaTrustworthyAI/CounterfactualExplanations.jl/releases/tag/v0.1.7). Unfortunately, a new release for that tag has **not** been automatically created and I don’t know why.

Perhaps this has to do with some default setting for the new organisation? Any help would be much appreciated!

Thanks

---

<div class="post-metadata">

**Author:** ![abelsiqueira](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/abelsiqueira/32/47269_2.png) [@abelsiqueira](https://discourse.julialang.org/u/abelsiqueira)\
**Post date:** [February 27, 2023, 12:57pm UTC](https://discourse.julialang.org/t/tagbot-release-for-new-version-not-automatically-triggered/95179/2 "2023-02-27T12:57:51Z")

</div>

Do you have [Julia TagBot · Actions · GitHub Marketplace · GitHub](https://github.com/marketplace/actions/julia-tagbot) in the new organization as well?

---

<div class="post-metadata">

**Author:** ![pat-alt](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pat-alt/32/34264_2.png) [@pat-alt](https://discourse.julialang.org/u/pat-alt)\
**Post date:** [February 28, 2023, 8:53am UTC](https://discourse.julialang.org/t/tagbot-release-for-new-version-not-automatically-triggered/95179/3 "2023-02-28T08:53:05Z")

</div>

Thanks @abelsiqueira, I have TagBot set up for each package repository. For the organisation, would I need to additionally configure a YAML [here](https://github.com/JuliaTrustworthyAI/.github)?

**Edit** : Or do I need to reset the deploy keys for each repo?

---

<div class="post-metadata">

**Author:** ![abelsiqueira](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/abelsiqueira/32/47269_2.png) [@abelsiqueira](https://discourse.julialang.org/u/abelsiqueira)\
**Post date:** [February 28, 2023, 9:22am UTC](https://discourse.julialang.org/t/tagbot-release-for-new-version-not-automatically-triggered/95179/4 "2023-02-28T09:22:04Z")

</div>

According to this line ([TagBot trigger issue · JuliaTrustworthyAI/CounterfactualExplanations.jl@d5b9d56 · GitHub](https://github.com/JuliaTrustworthyAI/CounterfactualExplanations.jl/actions/runs/4266944369/jobs/7428036990#step:3:58)) it looks like a permission failure. Can you check you [https://github.com/JuliaTrustworthyAI/CounterfactualExplanations.jl/settings/actions](https://github.com/JuliaTrustworthyAI/CounterfactualExplanations.jl/settings/actions) in “Workflow permissions” if “Read and write permissions” is enabled?

---

<div class="post-metadata">

**Author:** ![pat-alt](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pat-alt/32/34264_2.png) [@pat-alt](https://discourse.julialang.org/u/pat-alt)\
**Post date:** [February 28, 2023, 9:39am UTC](https://discourse.julialang.org/t/tagbot-release-for-new-version-not-automatically-triggered/95179/5 "2023-02-28T09:39:50Z")

</div>

Thanks a lot! It was read-only and enabling write access seems to have done something: the workflow now seems to run without issues: [TagBot trigger issue · JuliaTrustworthyAI/CounterfactualExplanations.jl@d5b9d56 · GitHub](https://github.com/JuliaTrustworthyAI/CounterfactualExplanations.jl/actions/runs/4266944369)

There’s still no new release for the tag, but I guess this may be due to the workflow being interrupted initially?

---

<div class="post-metadata">

**Author:** ![abelsiqueira](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/abelsiqueira/32/47269_2.png) [@abelsiqueira](https://discourse.julialang.org/u/abelsiqueira)\
**Post date:** [February 28, 2023, 9:48am UTC](https://discourse.julialang.org/t/tagbot-release-for-new-version-not-automatically-triggered/95179/6 "2023-02-28T09:48:58Z")

</div>

I would trigger it manually, just to be sure. But it could also be this lookback period ([Julia TagBot · Actions · GitHub Marketplace · GitHub](https://github.com/marketplace/actions/julia-tagbot#lookback-period)). They have a more up-to-date TagBot.yml, it looks like it even handles the permission issues directly. Haven’t tried it yet, though.

---

<div class="post-metadata">

**Author:** ![pat-alt](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pat-alt/32/34264_2.png) [@pat-alt](https://discourse.julialang.org/u/pat-alt)\
**Post date:** [March 2, 2023, 9:12am UTC](https://discourse.julialang.org/t/tagbot-release-for-new-version-not-automatically-triggered/95179/7 "2023-03-02T09:12:52Z")

</div>

All working now, thanks very much! (just pushed a new release for another [package](https://github.com/JuliaTrustworthyAI/ConformalPrediction.jl))

---

<div class="post-metadata">

**Author:** ![pat-alt](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pat-alt/32/34264_2.png) [@pat-alt](https://discourse.julialang.org/u/pat-alt)\
**Post date:** [March 10, 2023, 5:15pm UTC](https://discourse.julialang.org/t/tagbot-release-for-new-version-not-automatically-triggered/95179/8 "2023-03-10T17:15:46Z")

</div>

Another related [issue](https://discourse.julialang.org/t/error-deploying-documentation-after-moving-repo-to-organization/95877), thought I’d ping you here @abelsiqueira 😃 thanks again for you help!