Repository navigation
fix: restore native runtime compatibility and gate dependency merges - #715
Merged
Merged
Conversation
12 tasks done
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.
Summary
#706 updated ONNX Runtime without updating sherpa-onnx's native dependency. Both APK flavors then failed the packaged JNI compatibility check. Restore the compatible 1.27.0 runtime and prevent dependency updates from merging before the aggregate CI gate passes.
Changes
Required checksfrom GitHub Actions, including current-base validation, before enabling Dependabot auto-merge.Verification
node --test .github/scripts/check-dependabot-merge.test.cjs: 5 passed, including absent protection, wrong check, stale-base allowance, and wrong check producer.node .github/scripts/classify-ci-paths.test.cjs: passed.git diff --check: passed.devruleset was read back and accepted by the same policy validator. It requires the GitHub Actions aggregate check with strict current-base validation and no bypass actors.4ee237c56999873404ed6c0cdf47ac8fe64800a0: https://github.com/Codename-11/hermes-relay/actions/runs/38747586356. Both APK flavors passed native compatibility; Android lint/tests and the selected desktop, plugin, dashboard, docs, and contract checks passed. No phone installation or release.Screenshots
No UI change.
Compatibility / risk
Restores the existing Sherpa ABI baseline. The merge workflow fails closed if protection is removed or changed to an insufficient gate. Major upgrades remain manual. No production deployment or migration.
Lineage / contributor credit
86b5a27eaa50822ff63aa8e8beb205905fcd4364, authored byophirhan, cherry-picked with original authorship and source reference preserved.Checklist
dev