You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have reported already the same question on the original project but then found this one which seems to be actively maintained.
We are using semantic versioning (semver.org) in our projects and stumbled upon the following problem:
We have some projects that extend some other upstream projects with some functionality (eg. forks). We want to version our projects with the following semver schema:
1.2.3+4.2.1
1.2.3-SNAPSHOT+4.2.1
where 1.2.3 is our own version of the project and 4.2.1, the metadata part of semver, which reflects the upstream version our changes are based on.
When releasing our versions we would like to have the following flow:
Is it possible to implement this kind of workflow where the metadata part (eg. +4.2.1) won't be touched?
I have tried various things but did not come up with something that just leaves the metadata part.
Also it would be great to have one config that covers the case with +metadata and without it.
Thanks a lot.
The text was updated successfully, but these errors were encountered:
I like the independent flag -- on that note it may be a good idea to reach out to @andrivet and see if incorporating that will allow all use-cases supported by the fork to be supported by us so that we can cease the fork...
Hello,
I have reported already the same question on the original project but then found this one which seems to be actively maintained.
We are using semantic versioning (semver.org) in our projects and stumbled upon the following problem:
We have some projects that extend some other upstream projects with some functionality (eg. forks). We want to version our projects with the following semver schema:
where
1.2.3
is our own version of the project and4.2.1
, the metadata part of semver, which reflects the upstream version our changes are based on.When releasing our versions we would like to have the following flow:
Right now we use the following configuration:
Is it possible to implement this kind of workflow where the metadata part (eg.
+4.2.1
) won't be touched?I have tried various things but did not come up with something that just leaves the metadata part.
Also it would be great to have one config that covers the case with
+metadata
and without it.Thanks a lot.
The text was updated successfully, but these errors were encountered: