chore(release): trigger obfuscated loader release [Release]
Touch build.gradle (a paths-filtered file) so the push runs Build Loader; HEAD carries [Release], so the workflow cuts a GitHub Release with the obfuscated jar + injector + de-obfuscation mapping. Empty commits are skipped by the workflow's paths filter, hence a real (harmless comment) change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -713,3 +713,7 @@ tasks.register('cleanNative', Delete) {
|
|||||||
tasks.named('clean').configure {
|
tasks.named('clean').configure {
|
||||||
dependsOn 'cleanNative'
|
dependsOn 'cleanNative'
|
||||||
}
|
}
|
||||||
|
|
||||||
|
// Release builds are cut by .github/workflows/build-loader.yml when the head commit
|
||||||
|
// message contains [Release]. Every build emits fresh random class names — see
|
||||||
|
// ext.obfuscateJar above and the "编译时类名混淆" section in the README.
|
||||||
|
|||||||
Reference in New Issue
Block a user