[Feature Request] Expose BaseSemVer as Output Variables #4803
jakublatkowski
started this conversation in
Ideas
Replies: 1 comment
-
|
@jakublatkowski I guess we could at least have a look on a draft PR and understand better the motivation behind the changes |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Expose BaseSemVer in the output variables so CI pipelines can reference the base version.
Context
Some systems (e.g., SonarCloud) use semantic versioning to compare incremental code coverage. They require the previous (base) version to generate accurate incremental coverage reports.
Possible Implementation
Include BaseSemVer alongside existing version fields in the standard outputs (environment variables, JSON output, and any other supported output channels), enabling CI pipelines to consume it directly.
Motivation
Simplifies integrations that need the base version, avoiding custom parsing or brittle workarounds.
Contribution
I already have changes in my fork and I’m happy to open a PR if this addition is considered valuable.
Beta Was this translation helpful? Give feedback.
All reactions