-
Hi, I'm trying to set up this action in my new pipeline, but it keeps detecting the wrong version. https://github.com/mortenn/BrowserPicker/actions/runs/8499864106/job/23281113301
As we can see, it finds the v2.0.0-beta4 tag, but ignores that. I also tried doing a commit to main with "(MAJOR)" in the message, but it still showed up as 1.8.3:
I can probably work around this by adding a v2.0.0 tag I guess, but I haven't released it yet, so I don't really want to do that unless there is absolutely no way around the problem. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The change path basically adds a If you haven't seen this already, you might want to have a look at the guide for details on common configurations. |
Beta Was this translation helpful? Give feedback.
The change path basically adds a
-- ${CHANGE_PATH}
to all git commands is intended for fully independently versioning a sub project when you have multiple projects present and is typically used along with anamespace
param. With this enabled, only commits on that path are considered. You have a commit with(MAJOR)
which changes the readme, but this file isn't in the change path which is given as/src
so it won't be considered.If you haven't seen this already, you might want to have a look at the guide for details on common configurations.