Skip to content

Promote qualified Maven artifacts without rebuilding - #288

Merged
philipgreat merged 1 commit into
mainfrom
release/logging-qualified-promotion-20261118
Nov 18, 2026
Merged

philipgreat merged 1 commit into
mainfrom
release/logging-qualified-promotion-20261118

Conversation

@philipgreat

Copy link
Copy Markdown
Contributor

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.

Signed-off-by: Philip Z <hello@teaql.io>
@philipgreat
philipgreat merged commit 6365cf0 into main Nov 18, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant