Usage of the --unreleased argument gets parsed differently after v4.4.2

[APEX-BLAGOY-PAVLOV]

A setup for creation of a changelog is used in our GitHub actions, as follows:

steps:
  - name: Checkout Repository
    uses: actions/checkout@v4
    with:
      fetch-depth: 0

  - name: Generate Changelog
    uses: orhun/git-cliff-action@v4.5.0
    id: git-cliff
    with:
      config: .github/cliff.toml
      args: --strip all --unreleased --ignore-tags draft-
    env:
      OUTPUT: CHANGELOG.md

1. While the used version was v4.4.2, the "--unreleased" argument was taken into consideration, and the result came as expected - the action outputs only the latest changes, the ones not falling under any previous tags.
2. When fixing to v4.5.0, the action started outputting a changelog as if it takes all changes since a long time ago, not just the last ones, since the last tag. This brings to the conclusion that the "--unreleased" argument is not parsed correctly, and the git_cliff is picking all changes, inclusive of the already tagged ones.
3. On the other hand, with v4.6.0, the changelog comes out empty at all.

All above is happening on the same configs of the "cliff.toml" file, which were inspected and don't seem to have something in common with the case.

The same command arguments have been tested locally on git_cliff v2.7.0, as opposed to v2.10.0, and the behavior is equal between the two. Therefore, it seems that the difference comes from the action itself.
Change of the order of arguments has been tested with no result, as well as replacing the draft- pattern with "draft-*", again no result.

[orhun]

Hello! Thanks for reporting.

Interesting issue... Any chance that you could share the action logs?

For reference, here are the major changes made in the mentioned releases:

• 4.5.0 -> fix(args): allow setting the output via --output argument #53
• 4.6.0 -> fix(run): exit with correct exit code #58

#53 might be problematic, but I'm not sure why you are getting an empty changelog with 4.6.0...

[blajoppp]

The #53 was also the addition of code that I suspected in respect of the behavior change.
Unfortunately, the logs are largely connected with company sensitive info, due to the changelog prints in the company repo, so I can't share them.
What I did was fix the version to 4.4.2 as of now.

[orhun]

For reference, what I did in #53 was to collect the argument list and set the value of OUTPUT environment variable to whatever provided in --output.

Maybe I'm reconstructing $@ wrongly there and it thinks --unreleased is a part of another argument. Things you could try:

• Change the order of arguments you use and see if it takes any effect.
• Use quotes: args: '"--strip" "all" "--unreleased" "--ignore-tags" "draft-"'

[APEX-BLAGOY-PAVLOV]

During the investigation of our issue I tried playing around with the sequence of args, but unsuccessfully.
Now tried the quotes as well, like:
args: '"--strip" "all" "--unreleased" "--ignore-tags" "draft-"'
but again v4.5.0 produces a huge output and does not account for the --unreleased argument.
Thanks for your assistance, if anybody from the community has a similar problem, they can also comment.

[orhun]

Also, setting up a minimal repo with dummy commits and a CI setup described here would be helpful to see what's going on. (Basically a repro case)