Repository navigation
Promote qualified Maven artifacts without rebuilding - #288
Merged
Merged
Conversation
Signed-off-by: Philip Z <hello@teaql.io>
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.
The logging 6.3.0 files have already passed two clean installed consumers, but the existing tag workflow rebuilds with lifecycle deploy. Add a separate manual workflow that verifies the existing signed tag, the signed qualification digest, all 103 native artifact hashes and the complete 34-module boundary, then uploads those exact files using native Maven deploy-file and the existing protected Maven environment. No SDK source or version is changed.
Before the first write, all destination files are checked: conflicting bytes or a partially existing native group fail closed; complete identical groups can resume. Every uploaded file is read back and hashed, and the existing remote completeness verifier checks all modules and release metadata. Temporary downloads/plugin caches are removed on exit; compact receipts are uploaded on success or failure.
Validation: local preflight passed against the real signed v6.3.0 and all 103 qualified files. A modified-JAR negative control was rejected before any publication command. Workflow expressions use environment variables and validated inputs; secret values are never written to commands or receipts. Original SDK worktrees and artifacts remain untouched.
Tracking: #286 and teaql/teaql-conformance#248. The user has explicitly authorized the existing Java Maven publication credentials.