# Laminas/automatic-releases: how do you stop the milestones?

**URL:** <https://discourse.laminas.dev/t/laminas-automatic-releases-how-do-you-stop-the-milestones/1824>\
**Category:** Components & MVC\
**Created:** [September 12, 2020, 4:01pm UTC](https://discourse.laminas.dev/t/laminas-automatic-releases-how-do-you-stop-the-milestones/1824 "2020-09-12T16:01:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![greg0ire](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.laminas.dev/greg0ire/32/791_2.png) [@greg0ire](https://discourse.laminas.dev/u/greg0ire)\
**Post date:** [September 12, 2020, 4:01pm UTC](https://discourse.laminas.dev/t/laminas-automatic-releases-how-do-you-stop-the-milestones/1824/1 "2020-09-12T16:01:48Z")

</div>

I’m trying to [setup the `laminas/automatic-releases` workflow on `doctrine/dbal`](https://github.com/doctrine/dbal/pull/4251), and got a question about the milestone creation step in my review: what if we don’t need a milestone to be created, because this is the last patch version of this minor, or the last minor version of this major?

Will a milestone be created, and then we have to delete it manually?

---

<div class="post-metadata">

**Author:** ![xtreamwayz](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.laminas.dev/xtreamwayz/32/27_2.png) [@xtreamwayz](https://discourse.laminas.dev/u/xtreamwayz)\
**Post date:** [September 12, 2020, 6:10pm UTC](https://discourse.laminas.dev/t/laminas-automatic-releases-how-do-you-stop-the-milestones/1824/2 "2020-09-12T18:10:12Z")

</div>

The configuration is in the github workflow itself. Search for the `Create new milestones` step (it should be at the end) and remove it:

```auto
      - name: "Create new milestones"
        uses: "laminas/automatic-releases@v1"
        with:
          command-name: "laminas:automatic-releases:create-milestones"
        env:
          "GITHUB_TOKEN": ${{ secrets.GITHUB_TOKEN }}
          "SIGNING_SECRET_KEY": ${{ secrets.SIGNING_SECRET_KEY }}
          "GIT_AUTHOR_NAME": ${{ secrets.GIT_AUTHOR_NAME }}
          "GIT_AUTHOR_EMAIL": ${{ secrets.GIT_AUTHOR_EMAIL }}

```

If you don’t have a `CHANGELOG.md` file, you can also remove this step:

`- name: "Bump Changelog Version On Originating Release Branch"`

---

<div class="post-metadata">

**Author:** ![greg0ire](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.laminas.dev/greg0ire/32/791_2.png) [@greg0ire](https://discourse.laminas.dev/u/greg0ire)\
**Post date:** [September 12, 2020, 6:14pm UTC](https://discourse.laminas.dev/t/laminas-automatic-releases-how-do-you-stop-the-milestones/1824/3 "2020-09-12T18:14:49Z")

</div>

Sorry, apparently my question wasn’t precise enough; let’s say I have version 2.10.4 ready, but it is the last patch version for this branch. When I close milestone 2.10.4, version 2.10.4 is tagged, but then milestone 2.10.5 will be created, right? If 2.10.x is no longer maintained after 2.10.4, I will be left with a useless milestone, won’t I?

---

<div class="post-metadata">

**Author:** ![ocramius](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.laminas.dev/ocramius/32/23_2.png) [@ocramius](https://discourse.laminas.dev/u/ocramius)\
**Post date:** [September 24, 2020, 6:23am UTC](https://discourse.laminas.dev/t/laminas-automatic-releases-how-do-you-stop-the-milestones/1824/4 "2020-09-24T06:23:56Z")

</div>

Yes, but you can just delete that milestone then