Skip to content

Understanding what goes into each release/tag #471

@ericf

Description

@ericf

I've opened several issues requesting a changelog so I can understand what goes into each release of Handlebars, but we're not there yet.

I understand that the npm tags are different from the main release tags, but I cannot reason about what code I'm running.

1.0.0-rc.3 != v1.0.9: https://github.com/wycats/handlebars.js/compare/1.0.0-rc.3...v1.0.9?w=1

1.0.0-rc.3 != v1.0.10: https://github.com/wycats/handlebars.js/compare/1.0.0-rc.3...v1.0.10?w=1

1.0.0-rc.3 -> v1.0.9 -> v1.0.10 represents a large number of changes, all of which appear to be under RC-3. This tagging inconsistency combined with a lack of a changelog makes it very hard to keep up with the changes of this project.

Could you please make the following changes:

  • Add a changelog (pretty please!)
  • Use consistent tagging between releases and npm packages. (Or at least create two tags every time a new version is published somewhere.)

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions