anton-yurchenko/git-release

Any ideas why this is fails? Changelog does not contain changes for requested project version

RIP21 opened this issue ยท 4 comments

RIP21 commented

Take a look at this action:
https://github.com/RIP21/react-hanger-clone-for-course/runs/1141443576?check_suite_focus=true
(I hope it can be accessed)

I have the following changelog format:

# 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).

Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).

## [v0.0.2](https://github.com//RIP21/react-hanger-clone-for-course.git/compare/v0.0.1...v0.0.2)

### Commits

- Meaningful change [`de69c9d`](https://github.com//RIP21/react-hanger-clone-for-course.git/commit/de69c9d93b579cfaabc64c2b9c54c2c2fe1c227b)
- Meaningful change [`2b4a229`](https://github.com//RIP21/react-hanger-clone-for-course.git/commit/2b4a2295c1a3a0ef0523a09cc780e109d0e808c0)

## [v0.0.1](https://github.com//RIP21/react-hanger-clone-for-course.git/compare/v0.0.1-0...v0.0.1) - 2020-09-21

It argues that it can't find proper changelog version. Is it because it contains v inside like[v0.0.2] instead of [0.0.2]?

Output is following:

INFO version: 3.4.1                               
WARNING 'DRAFT_RELEASE' is not equal to 'true', assuming 'false' 
WARNING 'PRE_RELEASE' is not equal to 'true', assuming 'false' 
WARNING 'ALLOW_TAG_PREFIX' enabled                   
WARNING 'CHANGELOG_FILE' is not defined, assuming 'CHANGELOG.md' 
FATAL changelog does not contain changes for requested project version 

This is when it runs on a v0.0.2 tag push.

Thanks!

Looks like v prefix (...[v0.0.2]...) is causing this:

## [v0.0.2](https://github.com//RIP21/react-hanger-clone-for-course.git/compare/v0.0.1...v0.0.2)

You may also find a remark about this on readme.

RIP21 commented

@anton-yurchenko yes I noted that, but the wording was unclear so I just wanted to clarify that. Ok, good, so I'll try to generate without v then.
Thanks! :)

Cool! I'll rephrase that note to be more clear.
Thank you @RIP21.

RIP21 commented

Cheers man! Thank you for your job :)