layero 0.11.24 → 0.11.25

package/README.md

@@ -368,6 +368,12 @@ Full reference: <https://docs.layero.ru/cli/json-events>
 `node_modules`, `.git`, `dist`, `build`, `.next`, `.env*`, `.DS_Store`, and
 the rule files themselves. Maximum archive size is 500 MB.
 
+Env files (`.env`, `.env.*`) stay out even if `.gitignore` un-ignores them
+(`!.env.example`, `!.env`): those rules are written for git, not for a
+deploy. To upload an env file on purpose, name it in `.layeroignore`:
+`!.env.production`. Broad negations like `!*` do not bring env files back,
+and nothing brings back `.git`, `.layero` or the rule files.
+
 ## Config
 
 - Auth token: `~/.layero/config.json` (chmod 600). Claim tokens of temporary

package/dist/pack.js

@@ -60,11 +60,50 @@ const FORCE_INCLUDE_LOCKFILES = [
     "pnpm-lock.yaml",
     "npm-shrinkwrap.json",
 ];
-async function buildIgnore(cwd) {
+// Env files carry secrets. In the `ignore` package the last matching rule
+// wins, so a `.gitignore` written for git — `!.env.example`, or `!.env` in a
+// monorepo that commits a shared one — used to pull env files back into the
+// archive. A static site without a build serves the archive as-is, so that
+// `.env` ended up readable at the site's address.
+//
+// The exclusion is therefore re-applied after each user layer. The only way
+// back in is an explicit negation in `.layeroignore` that names an env file
+// (`!.env.production`): a deliberate, Layero-specific choice. `.gitignore`
+// never overrides it, and neither do broad `.layeroignore` negations such as
+// `!*`.
+//
+// The same broad negation would also have pulled back the other things that
+// must never reach a site: VCS metadata (remote credentials live in
+// `.git/config`), the CLI's own `.layero/` (claim tokens) and the rule files
+// themselves. They get the same treatment, with no way back in at all.
+const ENV_EXCLUDE = [".env", ".env.*"];
+const ALWAYS_EXCLUDE = [
+    ...ENV_EXCLUDE,
+    ".git",
+    ".svn",
+    ".hg",
+    ".layero",
+    ".gitignore",
+    ".layeroignore",
+];
+/** Negations from `.layeroignore` that explicitly name an env file. */
+function explicitEnvNegations(lines) {
+    return lines.filter((l) => l.startsWith("!") && l.includes(".env"));
+}
+async function userLayers(cwd) {
+    const gitignore = await readIgnoreFile(path.join(cwd, ".gitignore"));
+    const layeroignore = await readIgnoreFile(path.join(cwd, ".layeroignore"));
     const ig = ignore();
     ig.add(DEFAULT_IGNORE);
-    ig.add(await readIgnoreFile(path.join(cwd, ".gitignore")));
-    ig.add(await readIgnoreFile(path.join(cwd, ".layeroignore")));
+    ig.add(gitignore);
+    ig.add(ALWAYS_EXCLUDE);
+    ig.add(layeroignore);
+    ig.add(ALWAYS_EXCLUDE);
+    ig.add(explicitEnvNegations(layeroignore));
+    return ig;
+}
+async function buildIgnore(cwd) {
+    const ig = await userLayers(cwd);
     // Negations last so they win over any ignore rule above.
     ig.add(FORCE_INCLUDE_LOCKFILES.map((f) => `!/${f}`));
     return ig;
@@ -106,10 +145,7 @@ async function sha256OfFile(p) {
  * negations, so it reflects exactly what the user's .gitignore/.layeroignore
  * would have excluded. */
 async function detectForcedLockfiles(cwd) {
-    const probe = ignore();
-    probe.add(DEFAULT_IGNORE);
-    probe.add(await readIgnoreFile(path.join(cwd, ".gitignore")));
-    probe.add(await readIgnoreFile(path.join(cwd, ".layeroignore")));
+    const probe = await userLayers(cwd);
     const forced = [];
     for (const lf of FORCE_INCLUDE_LOCKFILES) {
         if (!probe.ignores(lf))

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "layero",
-  "version": "0.11.24",
+  "version": "0.11.25",
   "description": "Layero CLI — deploy a directory or a repo to hosting with build servers in Russia. JSON events and exit codes for AI agents and CI.",
   "license": "MIT",
   "type": "module",