6.1.0 update breaks functionality?!

[ulfgebhardt]

Describe the bug

After an update(Ocelot-Social-Community/Ocelot-Social#8830) to 6.1.0 the action fails

To reproduce

Failing on this PR Ocelot-Social-Community/Ocelot-Social#8835

Producing

Run amannn/action-semantic-pull-request@677b89571e961351de6fcbd96c8b2503787962e2
Error: No release type found in pull request title "feat(webapp): location distance in profile". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

See job: https://github.com/Ocelot-Social-Community/Ocelot-Social/actions/runs/17112221793/job/48535943105?pr=8835

Configuration: https://github.com/Ocelot-Social-Community/Ocelot-Social/blob/master/.github/workflows/test.lint_pr.yml

Note: The PR is a single commit.

Update: Also happens with multiple commits

Expected behavior

I don't see how the title should fail?! Is there a special character somewhere?

[amannn]

Thanks for opening this issue! I'm currently trying to reproduce this in #293 but have unfortunately failed so far.

Your workflow file references 677b89571e961351de6fcbd96c8b2503787962e2, which corresponds to v6.1.0.

There have been two relevant releases recently:

• v6.0.1 (which is basically v6.0.0, but without a bug that prevented the action from running at all)
• v6.1.0

Can you try to use v6.0.1 to see if this issue was introduced with v6.1.0?

/cc @G-Rath

[ulfgebhardt]

That would be fdd4d3ddf614fbcd8c29e4b106d3bbe0cb2c605d as in fdd4d3d

I can tell that it worked in 335288255954904a41ddda8947c8f2c844b8bfeb as seen in Ocelot-Social-Community/Ocelot-Social#8836

And after the revert it starts working again.

[amannn]

335288255954904a41ddda8947c8f2c844b8bfeb was still on the v5 range, the question currently is whether v6.0.1 (fdd4d3ddf614fbcd8c29e4b106d3bbe0cb2c605d) still worked (which would indicate that #292 broke this).

Can you verify this for your setup?

[ulfgebhardt]

6.0.1 still has the same problem - see https://github.com/Ocelot-Social-Community/Ocelot-Social/actions/runs/17129665412/job/48590226599?pr=8837

Meaning the breaking change must have happend between 335288255954904a41ddda8947c8f2c844b8bfeb and fdd4d3ddf614fbcd8c29e4b106d3bbe0cb2c605d, including the later.

[ulfgebhardt]

The error can also be seen on the linked PR above Ocelot-Social-Community/Ocelot-Social#8840 which is running fdd4d3ddf614fbcd8c29e4b106d3bbe0cb2c605d

[ulfgebhardt]

For debugging purposes: 3352882...fdd4d3d

On the first glance I cannot determine the problem. Is it build related? Does the production code execute correctly?

[G-Rath]

I've found the bug, will have a PR up shortly: #295