home.social

#changelog — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #changelog, aggregated by home.social.

  1. 1.0 — это не зрелость, это обещание. Что мы заморозили и что сломали за три дня до этого

    Первый тег проекта датирован 22 июля, шестого сентября вышла 1.0. Разница между 0.37 и 1.0 не в коде: 1.0 - это список того, что автор больше не имеет права менять. Что именно попало в замороженный контракт, что осталось снаружи и почему об этом тоже надо говорить вслух, во что обошлась заморозка - 31 переменная окружения переименована за три дня до неё - и что нашла репетиция обновления и отката на копии продовых данных, включая откат, который уходил в краш-луп вместо понятной ошибки.

    habr.com/ru/articles/1079154/

    #selfhosted #semver #версионирование #обратнаясовместимость #миграции #обновление #релиз #changelog #мониторинг

  2. Nice to finally put this project to bed today.

    After much heel dragging on my part, I've gotten #towncrier installed into ~24 of my repos.

    Now it's just going to be a part of my normal workflow.🎉

    #TinyVictories #Python #CHANGELOG

  3. Finally close to seeing the light at the end of the tunnel with my #towncrier adoption for my projects.

    Only four more repo's(out of 20ish) git logs to audit and assemble plausible CHANGELOGs.

    Did I _need_ to any of this work? No. No one is ever going to look at this.

    Did I learn a few new things, or at least burn into muscle memory commands/workflows that will be useful in the future? Absolutely.

    Glad that I put in the effort.

    git tag -n
    git tag -a <new_tag> <old_tag>^{}
    git log -1 --format=%ai <tag>

    #NoteToSelf #LessonsLearned #git #towncrier #CHANGELOG #python

  4. 🚨 Breaking news: #GIMP devs finally realized their #changelog is longer than a CVS receipt 🧾. Despite months of "internal" work, the world still waits breathlessly for that mythical GIMP 3.4 release 🌈—because who doesn't love software updates that take less time than a geological epoch? ⏳
    gimp.org/news/2026/08/16/dev-u #GIMP3.4 #softwareupdates #devnews #techhumor #HackerNews #ngated

  5. Finally getting some traction on adopting #towncrier into my projects.

    I've been dragging my heels for 6 months as auditing the git logs of ~20 4 year old projects has been terribly daunting/overwhelming.

    Just going to have to be more diligent going forward with documenting changes.
    Lesson learned.

    It's not really "self-documenting" until you actually document it. derp.🤪

    #Python #Changelog #documentation

  6. 📣 The new versions of BlueSpice 5.2.6 and 5.1.10 are now available for download.
    bluespice.com/download/

    Full details on the included improvements and bug fixes can be found in our Helpdesk:
    ➡️ en.wiki.bluespice.com/wiki/Set

  7. Naty S @eclecticpassions ·

    I updated almost all the and code that generates my favourite page on : the /⁠stats page.

    ➡️ burgeonlab.com/stats/

    With the new post types I’ve added recently: books, replies (separated out from notes), and RSVPs; I noticed some data on the graphs being incorrect...

    View full note: burgeonlab.com/notes/2026/0723

    This is post 71 of
    📈burgeonlab.com/tags/100daystoo

  8. 📣 Today is Patch Day 📣
    BlueSpice 5.2.4 and 5.1.8 are now available for download.
    bluespice.com/download/

    Find more information about included improvements and bug fixes in our helpdesk:
    ➡️ en.wiki.bluespice.com/wiki/Set

  9. Been playing around with #towncrier for the past couple of days.
    I like its approach to creating & updating changelogs(plus its support for both .md & .rst output)

    Between its clear tutorial and referencing pipx & pytest's usage of the package, I think it's going to be an easy add-on to my projects. Plus, I really need to get better disciplined at writing regular consistent #Changelog

    towncrier.readthedocs.io/en/st

    #Python

  10. i wrote this #python #cli #tool last year it's pretty good.

    #protokolo generates a #changelog from fragment files, kind of like #towncrier, but way less intelligently (in a good way). its purpose is to circumvent the problem where many #vcs commits attempt to edit the same section in the change log file, and they #mergeConflict all the time. (or worse, a pr that is merged late adds its change log to a previous release.)

    protokolo.readthedocs.io/en/st

    #development #programming #git

  11. I hate merge conflicts in my change logs.

    I'm aware of #towncrier, but it's a bit finicky and prescriptive.

    Is there another general-purpose #changelog generator, or is this something I'm going to end up writing myself?