Skip to content

need changelogs for apps #471

Closed as not planned
Closed as not planned

Description

@klinch0

need changelogs for apps

for example, I use something in production and am in no hurry to update it every time an update appears. But it happens that there are updates that fix critical bugs, so to understand where and what needs to be updated first, you need a changelog

Activity

  1. dosubot commented on Nov 7, 2024

    @dosubot

    Changelogs in the cozystack codebase are written in Markdown format and follow the structure based on Keep a Changelog. They include sections for "Added," "Changed," "Deprecated," "Removed," "Fixed," and "Security" to categorize changes. Critical bug fixes are typically listed under the "Fixed" section. For example, the changelog for the ExternalDNS Helm Chart includes several bug fixes in version [v1.15.0] [1].

    To continue talking to Dosu, mention # (@dosu).

  2. matthieu-robin commented on Dec 11, 2024

    @matthieu-robin
    Collaborator

    I'm agree with klinch0 we need more details about changelog. What's the impact of the upgrade? thanks image

  3. dosubot commented on Oct 19, 2025

    @dosubot

    Hi, klinch0. I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.

    Issue Summary:

    • You requested more detailed changelogs for apps to better prioritize updates, especially critical bug fixes.
    • The current changelogs follow the Keep a Changelog format with categorized sections like "Added," "Fixed," and "Security."
    • Examples such as the ExternalDNS Helm Chart were provided to illustrate the existing format.
    • Another user agreed with your request, emphasizing the need for more detailed impact information in changelogs.
    • The issue remains unresolved with no recent updates or proposed solutions.

    Next Steps:

    • Please let me know if this issue is still relevant to the latest version of the cozystack repository by commenting here.
    • If I do not hear back within 7 days, this issue will be automatically closed.

    Thank you for your understanding and contribution!

  4. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Oct 19, 2025
  5. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Oct 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

kind/documentationCategorizes issue or PR as related to documentation

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions