Repository navigation
ci(lt-reports): also publish the report fatjar as a release asset - #22
Closed
Tejas-Aggarwal-lt wants to merge 1 commit into
Closed
Tejas-Aggarwal-lt wants to merge 1 commit into
Tejas-Aggarwal-lt wants to merge 1 commit into
Conversation
GitHub Packages Maven needs a token even for public repos and rejects GitHub App tokens, and LambdatestIncPrivate now bans PATs, so zeus dev builds of hyperexecute-job-artefacts can't fetch karate-reports. A release asset on this public repo downloads without a token. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Adds a
publish release assetstep tolt-reports-cd.yml: on pushes tolt-reportsit attaches the karate-core fatjar askarate-reports-<version>.jarto releasev<project.version>.<lt.patch.version>(skipped if that release already exists). Job permissioncontents: read→writesoGITHUB_TOKENcan create the release. The GitHub Packages publish is unchanged.Why: hyperexecute-job-artefacts downloads this jar during its Docker build. GitHub Packages Maven needs a token even for public repos, rejects GitHub App tokens, and LambdatestIncPrivate now bans PATs, so zeus (dev cluster) builds get 403 on it. A release asset on this public repo downloads with no token. Consumer change: https://github.com/LambdatestIncPrivate/hyperexecute-job-artefacts/pull/64
Rollout note:
lt.patch.versionis still 4, so the run after merge createsv1.5.3.4and then the Maven step fails (1.5.3.4 already published). That red run is expected once. If the jar built from today'slt-reportsmust equal the published 1.5.3.4, attach that jar tov1.5.3.4by hand instead.Test plan
curl -fsSLO https://github.com/LambdaTest/karate/releases/download/v1.5.3.4/karate-reports-1.5.3.4.jarworks without auth🤖 Generated with Claude Code