Open mpkorstanje opened 2 years ago
Just ran into the same issue. Workaround:
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
## [0.0.0]
[Unreleased]: https://github.com/cucumber/blockly/compare/v0.0.0...HEAD
[0.0.0]: https://github.com/cucumber/blockly/compare/818c1c282d9a685c8b9924f39a153a04b14f6b9e...v0.0.0
Followed by git tag v0.0.0
Then it works.
Ran into the same issue on cucumber-ruby when releasing v9. We made the CHANGELOG.old.md
but the new changelog still needed a version (Essentially the same issue you commented on).
Our workaround was to include the last 2 versions manually formatted in the new changelog, then the rest got canned
👓 What did you see?
Given an unreleased project, I can't use
polyglot-release
to release it: