Repository navigation
ci: align builds and releases with kpermute - #44
Merged
Merged
Conversation
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.
Default checks now configure only JVM + Linux x64 in one Linux job.
-Ptargets.fullrestores all 11 targets for release validation, with Linux, macOS/iOS and Windows checks in parallel. This copies the merged kpermute baseline from Eignex/kpermute#39..githubfiles are byte-identical between the skema and kencode rollout branches. Publication verification reads the library name from settings; no repository-specific workflow fork is needed.Validation
check lintDocs koverXmlReport publishAllPublicationsToLocalStagingRepositorypassed, including Java 17/25 packaged tests, default ABI and three-publication verification.checkKotlinAbi githubReleaseAssets publishAllPublicationsToLocalStagingRepository -Ptargets.fullpassed; all 12 Maven publications and 12 GitHub publications passed metadata, artifact and checksum validation.Kencode-specific: preserve serialization/bignum dependencies, JVM example dependencies and
package.md. The consumer round-trips Base64/Base64URL/Base85/Base62, checks JDK Base64 compatibility and exercises the published bignum runtime dependency.