[TE-10262]: version lt-reports fatjar publish & drop CI on push#18
Merged
Conversation
GitHub Packages rejects re-publishing an immutable version (HTTP 409),
so the fixed `lt-reports` coordinate failed on every CD run after the
first. Publish under ${project.version}.${lt.patch.version} instead:
project.version tracks upstream karate unchanged, lt.patch.version is a
new LambdaTest-fork counter in the root pom (added, not appended, so the
Maven Central release coordinate stays clean). Bump it to republish.
Also drop the push trigger on lt-reports-ci so the build check runs only
on PRs and manual dispatch (CD still publishes on push to lt-reports).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
saurabh-prakash
force-pushed
the
TE-10262-lt-reports-versioning
branch
from
a879619 to
8c90199
Compare
saurabh-prakash
force-pushed
the
TE-10262-lt-reports-versioning
branch
from
8c90199 to
a724e43
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two fixes for the
lt-reportsreport-fatjar pipeline:lt-reports-cdpublished under a fixed coordinate (com.lambdatest:karate-reports:lt-reports). GitHub Packages treats released versions as immutable, so every run after the first failed with HTTP 409 Conflict (example run). It now publishes under${project.version}.${lt.patch.version}(e.g.1.5.3.1).lt-reports-cinow triggers only onpull_requestandworkflow_dispatch(CD still publishes on push tolt-reports). Supersedes the closed Update CI workflow to remove push trigger #17.Versioning scheme
karate-parent<version>keeps tracking upstream karate unchanged (1.5.3).lt.patch.versionproperty in the root pom is a separate LambdaTest-fork counter — added, not appended to the karate version, so the Maven Central release coordinate stays clean.project.version+.+lt.patch.version.To republish after a change: bump
lt.patch.versionin the root pom.The publish coordinate now changes per release, so
hyperexecute-postprocessing-service(which pulled the fixedlt-reportsURL) must be pointed at the bumped version after each publish. First publish from this branch lands at1.5.3.1.🤖 Generated with Claude Code