We do a put: dev-semver. The expectation is that value in a file <some-path>/dev would get updated with a commit message semver bump to 1.0.1 . This works perfectly fine when the resource does not do/need a rebase of the git repo.
However, when the put: dev-semver does an automatic rebase before pushing; the %version% is not substituted and remains as %version% in the commit message. Value in the file is updated correctly, only the commit message has issues.
Ex: semver bump to %version%
Hi,
We are using semver-resource v1.4.0. We have defined the resource as follows.
We do a
put: dev-semver
. The expectation is that value in a file<some-path>/dev
would get updated with a commit messagesemver bump to 1.0.1
. This works perfectly fine when the resource does not do/need a rebase of the git repo.However, when the
put: dev-semver
does an automatic rebase before pushing; the%version%
is not substituted and remains as %version% in the commit message. Value in the file is updated correctly, only the commit message has issues. Ex:semver bump to %version%