@gjsify/gamepad-native-linux-arm64 0.52.0 → 0.54.0

package/README.md

@@ -1,14 +1,5 @@
 # @gjsify/gamepad-native-linux-arm64
 
-> **No artifact in this tarball yet.** `linux-arm64` is declared by
-> `@gjsify/gamepad-native` and built by CI, but not committed to the repository:
-> prebuilds.yml's `build-prebuilds` job (linux-arm64 leg) builds and tests it; `commit-prebuilds` lands the first artifact on main after this package merges
->
-> The package exists so the artifact has somewhere to land — and so its npm name
-> is claimed before the release that first ships it. Until then installing it is
-> harmless and does nothing: `@gjsify/gamepad-native` finds no typelib and takes its
-> no-native path, exactly as if this package were absent.
-
 
 The **linux-arm64** native artifacts of [`@gjsify/gamepad-native`](https://www.npmjs.com/package/@gjsify/gamepad-native) — a shared
 library plus its GObject-Introspection typelib, and nothing else. There is no

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gjsify/gamepad-native-linux-arm64",
-    "version": "0.52.0",
+    "version": "0.54.0",
     "description": "linux-arm64 prebuilt native library + GObject-Introspection typelib for @gjsify/gamepad-native. Installed automatically on linux/arm64 as an optionalDependency of that package (ADR 0017) and skipped everywhere else. Contains no JavaScript.",
     "license": "MIT",
     "os": [
@@ -13,8 +13,8 @@
         "prebuilds"
     ],
     "gjsify": {
-        "platformsUncommitted": {
-            "linux-arm64": "prebuilds.yml's `build-prebuilds` job (linux-arm64 leg) builds and tests it; `commit-prebuilds` lands the first artifact on main after this package merges"
+        "glibcRequires": {
+            "linux-arm64": "2.38"
         },
         "platforms": [
             "linux-arm64"