genlayer 0.38.15 → 0.39.0

package/.github/workflows/smoke.yml

@@ -23,5 +23,21 @@ jobs:
 
       - run: npm ci
 
+      # Smoke tests shell out to `node dist/index.js` to exercise the
+      # compiled CLI — without a build first, that file doesn't exist
+      # and the `genlayer staking validators` assertion fails with
+      # MODULE_NOT_FOUND before it can hit the network at all.
+      - name: Build CLI
+        run: npm run build
+
+      # The staking subcommands need a keystore for the default account
+      # even for read-only listings (BaseAction loads the account to
+      # report "your stake"). Create a throwaway one with a known
+      # password so the subprocess test in tests/smoke.test.ts can run.
+      - name: Create default keystore for CLI subprocess tests
+        run: node dist/index.js account create --name default --password ci-smoke-test
+        env:
+          CI: true
+
       - name: Run smoke tests
         run: npm run test:smoke

package/.release-it.cjs

@@ -0,0 +1,87 @@
+/**
+ * release-it configuration.
+ *
+ * Converted from `.release-it.json` to `.cjs` so we can supply a custom
+ * `whatBump` function that caps the recommended bump at `minor`. Reason:
+ *
+ *   `@release-it/conventional-changelog` forwards the default bump logic to
+ *   `conventional-recommended-bump`, whose `conventionalcommits` preset always
+ *   returns `major` when any commit's body contains a "BREAKING CHANGE" footer
+ *   (case-insensitive) or a `!:` marker. That would silently jump this CLI
+ *   from 0.x → 1.0.0 on a single stray commit, which is never what we want.
+ *
+ * This override forces the recommended bump to stop at `minor`. A genuine
+ * major release still requires an operator to pass `release-it major`
+ * explicitly, which is how most mature TS libraries handle it.
+ *
+ * `.release-it.json` takes precedence over `.release-it.cjs` in release-it's
+ * config resolution order, so the JSON file must not exist.
+ */
+
+module.exports = {
+  git: {
+    commitMessage: "Release v${version} [skip ci]",
+    tagName: "v${version}",
+    requireCleanWorkingDir: false,
+    requireUpstream: false,
+    requireCommits: false,
+    push: true,
+  },
+  github: {
+    release: true,
+    tokenRef: "GITHUB_TOKEN",
+  },
+  npm: {
+    publish: true,
+    publishArgs: ["--provenance --access public"],
+    skipChecks: true,
+  },
+  plugins: {
+    "@release-it/conventional-changelog": {
+      preset: "conventionalcommits",
+      infile: "CHANGELOG.md",
+      /**
+       * Cap automatic bumps at minor. Levels: 0 = major, 1 = minor, 2 = patch.
+       *   BREAKING CHANGE footer or `!:` marker → minor (was: major)
+       *   feat:                                  → minor (unchanged)
+       *   fix: / chore: / etc.                   → patch (unchanged)
+       * Run `release-it major` manually for a genuine major release.
+       */
+      whatBump: (commits) => {
+        const hasBreaking = commits.some((c) => {
+          const bangMarker = typeof c.header === "string" && /^[^:!\s]+!:/.test(c.header);
+          const breakingFooter =
+            Array.isArray(c.notes) && c.notes.some((n) => /BREAKING[ -]CHANGE/i.test(n.title ?? ""));
+          return bangMarker || breakingFooter;
+        });
+        const hasFeat = commits.some((c) => c.type === "feat");
+
+        if (hasBreaking) {
+          return {
+            level: 1,
+            reason:
+              "BREAKING CHANGE detected; auto-bump capped at minor. Run `release-it major` to force a major release.",
+          };
+        }
+        if (hasFeat) {
+          return { level: 1, reason: "feat commits present → minor" };
+        }
+        return { level: 2, reason: "no feat/breaking commits → patch" };
+      },
+      types: [
+        { type: "feat", section: "Features" },
+        { type: "fix", section: "Bug Fixes" },
+        { type: "chore", section: "Improvement Tasks" },
+        { type: "ci", section: "Continuous Integration" },
+        { type: "docs", section: "Documentation" },
+        { type: "style", section: "Styles" },
+        { type: "refactor", section: "Refactor Tasks" },
+        { type: "perf", section: "Performance Improvements" },
+        { type: "test", section: "Testing" },
+      ],
+    },
+  },
+  hooks: {
+    "after:bump": "npm run build",
+  },
+};

package/CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog
 
+## 0.39.0 (2026-04-23)
+
+### ⚠ BREAKING CHANGES
+
+* **release:** footer or `!:` marker.
+
+Background: a stray "BREAKING CHANGE:" line in any commit body would
+trip `conventional-recommended-bump` into recommending a major release,
+which in this CLI's current 0.38.x state would instantly ship 1.0.0
+without any intended stability declaration. Matching the fix applied
+
+### Miscellaneous Chores
+
+* **release:** cap auto-bumps at minor to avoid accidental majors ([#295](https://github.com/genlayerlabs/genlayer-cli/issues/295)) ([d0b5519](https://github.com/genlayerlabs/genlayer-cli/commit/d0b551931499c7c666ad27dfd6be21f9cd5f8db1)), closes [#159](https://github.com/genlayerlabs/genlayer-cli/issues/159)
+
+## 0.38.16 (2026-04-22)
+
+### Bug Fixes
+
+* **account:** send parses plain integer as wei, not GEN ([#294](https://github.com/genlayerlabs/genlayer-cli/issues/294)) ([660e745](https://github.com/genlayerlabs/genlayer-cli/commit/660e745678c717eeff3f0a5496203c8a4952e680)), closes [genlayer-js#155](https://github.com/genlayerlabs/genlayer-js/issues/155)
+
 ## 0.38.15 (2026-04-14)
 
 ### Bug Fixes