From 48a04d2d2da8ee3f0f7900ebd6cf0780040a0462 Mon Sep 17 00:00:00 2001
From: mkorwel <matt.korwel@gmail.com>
Date: Fri, 24 Oct 2025 09:45:50 -0700
Subject: [PATCH] chore: run preflight checks

---
 CONTRIBUTING.md               | 4 +++-
 scripts/configure-registry.js | 6 ++----
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 317b33bf44..fac4279ff4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -287,6 +287,7 @@ General contributors who only use the public `npmjs.org` registry may not need
 to perform this setup.
 
 This project uses a hybrid registry model:
+
 - Production packages (e.g., `@google/gemini-cli`) are published to `npmjs.org`.
 - Pre-release and development packages (e.g., `@google-gemini/gemini-cli`) are
   published to **GitHub Packages**.
@@ -309,7 +310,8 @@ This command will:
 2.  **Back up** your existing `~/.npmrc` to `~/.npmrc.bak` if a backup doesn't
     already exist.
 3.  **Overwrite** your `~/.npmrc` with the correct configuration to pull
-    packages from both `npmjs.org` and `npm.pkg.github.com` based on their scope.
+    packages from both `npmjs.org` and `npm.pkg.github.com` based on their
+    scope.
 
 After running this, you can install packages from both registries without any
 further configuration. If your GitHub token expires, you can simply run the
diff --git a/scripts/configure-registry.js b/scripts/configure-registry.js
index 39871deda9..8e78ddc726 100644
--- a/scripts/configure-registry.js
+++ b/scripts/configure-registry.js
@@ -109,9 +109,7 @@ function setupNpmrc() {
 
   fs.writeFileSync(npmrcPath, newContent);
   console.log(`✅ Successfully configured your ~/.npmrc file.`);
-  console.log(
-    'You can now install both production and pre-release packages.',
-  );
+  console.log('You can now install both production and pre-release packages.');
 }
 
-setupNpmrc();
\ No newline at end of file
+setupNpmrc();