Changelog History
Page 1
-
v5.2.3 Changes
April 18, 2021- 🛠 Fix bug preventing page titles from being displayed
-
v5.2.1 Changes
February 25, 2021- 🛠 Fix include call to a missing asset (@benjaminwil). This caused slow first page loads on JRuby.
-
v5.2 Changes
February 24, 2021- 👌 Improved styling and Primer upgrade (@benjaminwil)
- ➕ Add redirect to rename commit (@ViChyavIn)
- ⚡️ Updated dependencies
- 🛠 Bugfixes
-
v5.1.2 Changes
- Guard against malicious filenames in breadcrumbs
-
v5.1 Changes
- 🛠 Bugfixes
- ➕ Add autosave feature (#1576)
- ➕ Add Add quick access to diff of each commit in the history
-
v5.0.1
April 04, 2020 -
v5.0 Changes
March 17, 2020🛠 This is a major new release that introduces many new features, bugfixes, and removes major limitations. See here for a list of changes.
Note: due to changes to the way in which Gollum handles filenames, you may have to change some links in your wiki when migrating from gollum 4.x. See the release notes for more details. You may be find the
bin/gollum-migrate-tags
script helpful to accomplish this. Also see the--lenient-tag-lookup
option for making tag lookup backwards compatible with 4.x, though note that this will decrease performance on large wikis with many tags.Many thanks to all the users who have provided feedback, and everyone who has chipped in in the development process!
0️⃣ Many of these changes have been made possible by removing the default grit adapter in favour of the new rugged adapter.
-
v4.1.4 Changes
January 10, 2018- 👀 Depend on new version of gollum-lib that relies on a patched version of sanitize, which solves a vulnerability (CVE-2018-3740). See https://github.com/gollum/gollum-lib/pull/296.
-
v4.1.3 Changes
September 17, 2018- Solves a vulnerability in the File view and All Pages view that would allow XSS.
-
v4.1.2 Changes
August 07, 2017- ⚡️ Lock to a newer version of gollum-lib to avoid installing an outdated and vulnerable dependency (nokogiri) on ruby 2.0. See https://github.com/gollum/gollum-lib/pull/279. Note: this breaks semantic versioning so those using outdated rubies will discover the problem on update.