# Minor release 12.2.2?
**URL:** https://forum.graphviz.org/t/minor-release-12-2-2/2661
**Category:** Uncategorized
**Created:** [January 14, 2025, 7:36pm UTC](https://forum.graphviz.org/t/minor-release-12-2-2/2661 "2025-01-14T19:36:59Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@dallured](https://forum.graphviz.org/u/dallured)
#### Post date: [January 14, 2025, 7:36pm UTC](https://forum.graphviz.org/t/minor-release-12-2-2/2661/1 "2025-01-14T19:36:59Z")
In the change log I see an upcoming major release 13.0, with many breaking changes. How much trouble would it be to make an intermediate minor release with only recent bug fixes, and no breaking changes?
---
### Author:  [@mark](https://forum.graphviz.org/u/mark)
#### Post date: [January 15, 2025, 7:41am UTC](https://forum.graphviz.org/t/minor-release-12-2-2/2661/2 "2025-01-15T07:41:40Z")
Could you share some more context? Are you particularly worried about any of the breaking changes; how will they impact you?
We have always done linear releases in the past and it would be a bit of work to change that.
---
### Author:  [@dallured](https://forum.graphviz.org/u/dallured)
#### Post date: [January 15, 2025, 9:32am UTC](https://forum.graphviz.org/t/minor-release-12-2-2/2661/3 "2025-01-15T09:32:32Z")
@mark Thanks for your quick reply. Short answer: Never mind, I withdraw this request. It is not needed any more.
Details:
1. I was hoping for a bugfix minor release to harvest the fix for [issue 2631](https://gitlab.com/graphviz/graphviz/-/issues/2631) (completed). This was to fix [MacPorts issue #71615](https://trac.macports.org/ticket/71615). I wanted to compare the amount of work to create a Macports patch, versus the work to add this Graphviz minor release. Reading between the lines of your comment, it is far less work to patch MacPorts, rather than to interrupt the Graphviz normal release procedure at this time. Therefore the request is not justified.
2. Someone else beat me to that Macports patch before I could even think about it. So, minor release is not needed!
---
### Author:  [@mark](https://forum.graphviz.org/u/mark)
#### Post date: [January 15, 2025, 10:35am UTC](https://forum.graphviz.org/t/minor-release-12-2-2/2661/4 "2025-01-15T10:35:26Z")
Oh, wow. Impressive how fast the macports folks can patch things!
---
### Author:  [@dallured](https://forum.graphviz.org/u/dallured)
#### Post date: [January 15, 2025, 4:12pm UTC](https://forum.graphviz.org/t/minor-release-12-2-2/2661/5 "2025-01-15T16:12:19Z")
It often does not work that way. This particular Graphviz flaw was on someone’s radar because it was a “current issue”, causing trouble for dependants elsewhere.
---
### Author:  [@dallured](https://forum.graphviz.org/u/dallured)
#### Post date: [January 15, 2025, 4:14pm UTC](https://forum.graphviz.org/t/minor-release-12-2-2/2661/6 "2025-01-15T16:14:16Z")
I counted 206 dependents of Graphviz currently in Macports.
`port list depends:graphviz | wc -l`
---
### Author:  [@smattr](https://forum.graphviz.org/u/smattr)
#### Post date: [January 16, 2025, 9:22am UTC](https://forum.graphviz.org/t/minor-release-12-2-2/2661/7 "2025-01-16T09:22:02Z")
Ryan Schmidt is coincidentally both the Macports Graphviz maintainer and a maintainer of Macports itself, thus quite proactive. It is not uncommon for him to patch a fix into the Macports Graphviz package prior to a fix landing in Graphviz itself. I expect him to backport e.g. [smyrna: fix crash when trying to edit attributes with no open graph (!4187) · Merge requests · graphviz / graphviz · GitLab](https://gitlab.com/graphviz/graphviz/-/merge_requests/4187) too.