Fix Java and Swift documentation builds - #57
Merged
Merged
Conversation
why: Current Java sources split registrations out of Catalog.java and qualify factory calls. Docs publication rejects all runtime tool names when extraction reads only the older catalog layout. what: - Read Catalog and the toolset classes with qualified factory calls - Keep source registration and runtime schema agreement mandatory - Verify both layouts and the registered source file and line Validation: all 45 tools from the native Java server match source sites. The old extractor fails that run; the replacement passes. The outer docs loop passes in 48.5 seconds, including type and browser checks.
why: The setup-swift v2 release catalog rejects Swift 6.2.4 before the reference build starts. The selected source already pins that compiler. what: - Use mise-action v5.0.0 at its verified commit with mise 2026.9.17 - Install only the selected Swift version with GPG verification enabled - Disable caches, shims and unrelated environment exports - Verify the compiler version before adding its bin directory to PATH Validation: version checks reject a wrong or unreadable version. The installed 6.2.4 passes. The outer docs loop passes in 48.5 seconds. Actionlint retains the same eight unsupported GitHub job-context diagnostics; hosted installation and publication remain to be verified. Releases: https://github.com/jdx/mise-action/releases/tag/v5.0.0 https://github.com/jdx/mise/releases/tag/v2026.9.17
This was referenced Sep 30, 2026
This branch was successfully deployed
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.
Java and Swift documentation builds currently stop before publishing the complete capture and attach examples. Java's tool registrations moved into toolset classes, and the Swift setup action's release catalog rejects the compiler pinned by the selected source.
Java catalog extraction now reads both layouts and qualified factory calls while requiring agreement with runtime tool schemas. Swift setup uses a pinned stable mise action and installer, retains signature verification, and checks the installed compiler version before making it available to the build. The source revision still controls the exact Swift version.
Validation:
46f49ed0e4ab35a696d3323ca5a1446652067ad4exposes 45 tools. The old extractor rejects all 45; the new extractor matches every schema and source line.job.workflow_repository/job.workflow_shadiagnostics before and after.