Skip to content

Automate Release notes/changelog #59

@sscholle

Description

@sscholle

User Story

As a: Developer

I want to: know what features changed/added at which release version

Because: because it is useful to know what changes need to be implemented in a project that uses a specific version of a package

Additional Context

Add any context, screenshots, designs, links, etc. about the feature request here.

let's rather use release notes for this- I don't think this is a sustainable way of doing releases.

My suggestion is to use squash commits + annotated tags + git notes + git whatchanged {old_version}...{new version} when we do a release

We can turn this into an issue for future discussion

Acceptance Criteria

List of conditions that mark the story as complete

  • automate release notes
  • TODO...

Edge cases

List of edge cases to be considered when marking the story as complete

  • [ ]

Technical Description (not required initially)

A technical description of the problem, this should be completed by the engineering manager/developer

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions