Skip to content

Having such project without maintaining a proper changelog (with at least a note of breaking changes) should be given as an example of how not to publish packages #144

@jziolkowski

Description

@jziolkowski

Don't get me wrong. It's a great little package. Very useful.

But changelogs are there for a reason.

I'm tasked with updating your package (among almost 100 others) in a huge, albeit old, codebase.

Lack of changelog makes my work 10x more inefficient and, ultimately, more expensive.

/rant

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions