From: Matthew Fernandez Date: Sun, 11 Sep 2022 02:56:21 +0000 (-0700) Subject: Stable release 6.0.1 X-Git-Tag: 6.0.1^2 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=af85a9ee045fd6d0ba9e379e99f442ee7864e4d5;p=graphviz Stable release 6.0.1 The 6.0.0 release was bungled, resulting in multiple commits¹ that claimed to be Graphviz 6.0.0. ddd69c589483b31f589834e49ae902142cd4df38 of the website repository² deleted the 6.0.0 download links and we have deleted the 6.0.0 tag in this repository. This commit updates the changelog to indicate there was no 6.0.0 release and the next release will be 6.0.1. Hopefully things will go smoother this time around. Unfortunately the situation with 6.0.0 was predictable. Discussion on #2202 covered a hole in the release procedure, which turned out to be the exact problem that occurred. ¹ 9c4299601b40e5856df9a37cae78265ed2eb33b8 and 091148d2910ac5f9b4d3b14578da2623f47e347b. ² https://gitlab.com/graphviz/graphviz.gitlab.io --- diff --git a/CHANGELOG.md b/CHANGELOG.md index db12db778..1d21f0175 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,9 +4,7 @@ All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). -## [Unreleased (6.0.1)] - -## [6.0.0] – 2022-09-10 +## [6.0.1] – 2022-09-11 ### Changed @@ -1809,8 +1807,7 @@ March 13, 2000: Use AM_PROG_LIBTOOL instead of AC_PROG_LIBTOOL in configure.in. John Ellson ``` -[Unreleased (6.0.1)]: https://gitlab.com/graphviz/graphviz/compare/6.0.0...main -[6.0.0]: https://gitlab.com/graphviz/graphviz/compare/5.0.1...6.0.0 +[6.0.1]: https://gitlab.com/graphviz/graphviz/compare/5.0.1...6.0.1 [5.0.1]: https://gitlab.com/graphviz/graphviz/compare/5.0.0...5.0.1 [5.0.0]: https://gitlab.com/graphviz/graphviz/compare/4.0.0...5.0.0 [4.0.0]: https://gitlab.com/graphviz/graphviz/compare/3.0.0...4.0.0