Skip to content

Fix changelog generation

Laurent Canis requested to merge laucans/enforce-changelog-generation-for-release into dev

Motivation and Context

Fix the changelog generation, KO for last release.

Description

Changelog was KO because not regenerated during the tag (it was taken from cache) That's due to how hash is calculated. There is no changelog entry when we did a release, so the old one without the release is taken.

Fixed by adding, a condition on generation.

I will generate an entry to fix the website

Component

  • compiler
  • website
  • webide
  • vscode-plugin
  • debugger

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Performance improvement (non-breaking change that improves performance)
  • None (change with no changelog)

Changelog

Checklist:

  • If a new syntax has been introduced, put a message on slack ligo-lsp
  • Changes follow the existing coding style (use dune @fmt to check).
  • Tests for the changes have been added (for bug fixes / feature).
  • Documentation has been updated.
  • Changelog description has been added (if appropriate).
  • Start titles under ## Changelog section with #### (if appropriate).
  • There is no image or uploaded file in changelog
  • Examples in changed behaviour have been added to the changelog (for breaking change / feature).

Merge request reports