From 07be28c11e027de1aac955b60d44a6578d6def85 Mon Sep 17 00:00:00 2001
From: Shirona1337 <shirona@ichinomiya.dev>
Date: Mon, 1 Jun 2026 15:19:44 +0800
Subject: [PATCH] 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>
---
 build.gradle | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/build.gradle b/build.gradle
index 486dbb6..5e56776 100644
--- a/build.gradle
+++ b/build.gradle
@@ -713,3 +713,7 @@ tasks.register('cleanNative', Delete) {
 tasks.named('clean').configure {
     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.