genlayer 0.39.0 → 0.39.2

package/.github/workflows/publish.yml

@@ -1,39 +1,29 @@
-name: Release & Publish Package to NPM
+name: Publish Package to NPM
 
+# Tag-driven publish. The release is cut by a human (or Claude via the
+# release skill) running scripts/release.sh on the target stable branch
+# — that script bumps package.json, updates CHANGELOG.md, commits,
+# tags vX.Y.Z, and pushes both the branch commit and the tag. This
+# workflow fires on the tag push, sanity-checks the tag matches
+# package.json, builds, publishes to npm, and creates the GitHub
+# Release. It never bumps or tags by itself.
 on:
   workflow_dispatch:
   push:
-    branches:
-      - main
-      - staging
-    paths-ignore:
-      - 'docs/**'
+    tags:
+      - "v*"
 
 permissions:
   contents: write
   id-token: write
 
 jobs:
-  release:
+  publish:
     runs-on: ubuntu-latest
-    environment: npm
+    environment: Publish
     steps:
-      - name: Get CI Bot Token
-        uses: tibdex/github-app-token@v2
-        id: ci_bot_token
-        with:
-          app_id: ${{ secrets.CI_BOT_APP_ID }}
-          private_key: ${{ secrets.CI_BOT_SECRET }}
-
-      - name: Checkout source code
+      - name: Checkout tag
         uses: actions/checkout@v4
-        with:
-          token: ${{ steps.ci_bot_token.outputs.token }}
-
-      - name: Initialize Git User
-        run: |
-          git config --global user.email "github-actions[bot]@genlayer.com"
-          git config --global user.name "github-actions[bot]"
 
       - uses: actions/setup-node@v4
         with:
@@ -42,12 +32,36 @@ jobs:
 
       - run: npm ci
 
-      - name: Release
+      - name: Verify tag matches package.json version
         run: |
-          if [ "${{ github.ref_name }}" = "staging" ]; then
-            npm run release-beta
-          else
-            npm run release
+          TAG_VERSION="${GITHUB_REF_NAME#v}"
+          PKG_VERSION="$(node -p "require('./package.json').version")"
+          if [ "$TAG_VERSION" != "$PKG_VERSION" ]; then
+            echo "Tag ($TAG_VERSION) and package.json ($PKG_VERSION) disagree — refusing to publish." >&2
+            echo "Re-cut the release via scripts/release.sh so the tag and the committed version match." >&2
+            exit 1
           fi
+          echo "Tag $GITHUB_REF_NAME matches package.json $PKG_VERSION."
+
+      - run: npm run build
+
+      - name: Publish to npm
+        run: npm publish --provenance --access public
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+      - name: Create GitHub Release
         env:
-          GITHUB_TOKEN: ${{ steps.ci_bot_token.outputs.token }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          NOTES="$(awk -v ver="$GITHUB_REF_NAME" '
+            $0 ~ "^## \\[?" substr(ver, 2) {capture=1; next}
+            capture && /^## / {exit}
+            capture {print}
+          ' CHANGELOG.md)"
+          if [ -z "$NOTES" ]; then
+            NOTES="Release $GITHUB_REF_NAME"
+          fi
+          gh release create "$GITHUB_REF_NAME" \
+            --title "$GITHUB_REF_NAME" \
+            --notes "$NOTES"

package/.github/workflows/{cli-docs.yml → sync-docs.yml}

@@ -10,6 +10,7 @@ jobs:
     # Skip for pre-releases (tags containing '-') unless manually dispatched
     if: github.event_name != 'release' || !contains(github.event.release.tag_name, '-')
     runs-on: ubuntu-latest
+    environment: Sync-docs
     permissions:
       contents: read
     steps:
@@ -44,29 +45,11 @@ jobs:
           DOCS_VERSION: ${{ steps.version.outputs.value }}
         run: node scripts/generate-cli-docs.mjs | cat
 
-      - name: Set up Git (for committing to CLI repo)
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-
-      - name: Commit and push docs back to CLI repo (non-beta releases)
-        if: github.event_name == 'release' && !contains(github.event.release.tag_name, '-')
-        run: |
-          set -euo pipefail
-          if [ -n "$(git status --porcelain docs/api-references || true)" ]; then
-            git add docs/api-references
-            VERSION=${{ steps.version.outputs.value }}
-            git commit -m "docs(cli): update API reference for ${VERSION}"
-            git push
-          else
-            echo "No docs changes to commit"
-          fi
-
       - name: Generate docs repo token
         id: app-token
-        uses: actions/create-github-app-token@v1
+        uses: actions/create-github-app-token@v3
         with:
-          app-id: ${{ vars.DOCS_SYNC_APP_ID }}
+          client-id: ${{ vars.DOCS_SYNC_APP_CLIENT_ID }}
           private-key: ${{ secrets.DOCS_SYNC_APP_KEY }}
           repositories: genlayer-docs
 

package/.github/workflows/validate-code.yml

@@ -8,7 +8,7 @@ on:
       - reopened
   push:
     branches:
-      - main
+      - v0.39
 
 jobs:
   build-and-test:

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # Changelog
 
+## [0.39.2](https://github.com/genlayerlabs/genlayer-cli/compare/v0.39.1...v0.39.2) (2026-06-11)
+
+### Features
+
+* add v0.6 fee-aware commands ([#340](https://github.com/genlayerlabs/genlayer-cli/issues/340)) ([ca083ab](https://github.com/genlayerlabs/genlayer-cli/commit/ca083abbf854960a6638d5af63096b532a03cc5a))
+* branch-per-major release model ([#311](https://github.com/genlayerlabs/genlayer-cli/issues/311)) ([6fd2f3a](https://github.com/genlayerlabs/genlayer-cli/commit/6fd2f3a678ce348c92470828b03bdfc596afa9cb)), closes [genlayer-js#172](https://github.com/genlayerlabs/genlayer-js/issues/172)
+
+### Bug Fixes
+
+* **localnet:** print validator count to stdout ([37519e1](https://github.com/genlayerlabs/genlayer-cli/commit/37519e18b6155bc762fa24ea809a53c3e83ac9a7))
+* run CI on v0.39 branch ([#322](https://github.com/genlayerlabs/genlayer-cli/issues/322)) ([e129bab](https://github.com/genlayerlabs/genlayer-cli/commit/e129bab0c471c2d59d360b5ca8c1cb3190774ff8))
+* **system:** handle command-check and version parse failures ([#349](https://github.com/genlayerlabs/genlayer-cli/issues/349)) ([5b93dd3](https://github.com/genlayerlabs/genlayer-cli/commit/5b93dd32e45683f30368d0c9324078800c3d8dda)), closes [#301](https://github.com/genlayerlabs/genlayer-cli/issues/301) [#303](https://github.com/genlayerlabs/genlayer-cli/issues/303)
+
+## 0.39.1 (2026-05-06)
+
+### Bug Fixes
+
+* **ci:** add trigger comment to publish workflow ([#300](https://github.com/genlayerlabs/genlayer-cli/issues/300)) ([f3eeb99](https://github.com/genlayerlabs/genlayer-cli/commit/f3eeb99ce4e9222e9ba1bd9f6d31faf0e11bd380)), closes [#297](https://github.com/genlayerlabs/genlayer-cli/issues/297) [#298](https://github.com/genlayerlabs/genlayer-cli/issues/298)
+
 ## 0.39.0 (2026-04-23)
 
 ### ⚠ BREAKING CHANGES

package/CONTRIBUTING.md

@@ -31,6 +31,30 @@ Have ideas for new features or use cases? We're eager to hear them! But first:
 - Ensure you have the CLI installed to explore existing functionality.
 - After familiarizing yourself with the CLI, contribute your unique use case and share your ideas in our [Discord channel](https://discord.gg/8Jm4v89VAu).
 
+## Branch model
+
+This repo uses a branch-per-major release model. There is no `main`.
+
+- **`v0.39`** — current stable major (semver-zero, so 0.39 IS the major; 0.40 would be a major bump that gets its own branch). PRs for bug fixes / non-breaking features target this branch.
+- **`v<next>-dev`** — when next-major work is in progress, this branch is open for breaking changes. PRs introducing them target this branch.
+- **Older majors** stay for back-ports. Default branch on github.com is whichever major is current stable.
+
+When you fork or clone, the default branch is `v0.39` today. If you have a `main` branch from a previous checkout, delete it locally:
+
+```sh
+git checkout v0.39
+git branch -D main
+git remote prune origin
+```
+
+The previous `staging` branch (beta channel) has been retired. Pre-releases now go through the same release script with an explicit version (`scripts/release.sh 0.39.2-beta.0`).
+
+## Releases
+
+Releases are deliberate, not automatic. `scripts/release.sh` bumps the version, updates `CHANGELOG.md`, commits, tags, and pushes; CI takes over from the tag push and publishes to npm. See `.claude/skills/release/SKILL.md` for the full flow.
+
+**Semver-zero rule**: this package is on 0.x, so minor IS the breaking-change boundary. `0.39 → 0.40` is a major bump and needs a new branch — the script refuses `minor`/`major` keywords without `--allow-major`.
+
 ### Bug fixing and Feature development
 
 #### 1. Set yourself up to start coding

package/README.md

@@ -169,11 +169,15 @@ USAGE:
    genlayer deploy [options]
    genlayer call <contractAddress> <method> [options]
    genlayer write <contractAddress> <method> [options]
+   genlayer estimate-fees [contractAddress] [method] [options]
    genlayer schema <contractAddress> [options]
 
 OPTIONS (deploy):
    --contract <contractPath>  (Optional) Path to the intelligent contract to deploy
    --rpc <rpcUrl>             RPC URL for the network
+   --fees <json>              Transaction fee options JSON passed to genlayer-js
+   --fee-value <wei>          Explicit fee deposit value
+   --valid-until <timestamp>  Unix timestamp after which the transaction is invalid
    --args <args...>           Contract arguments (see Argument Types below)
 
 OPTIONS (call):
@@ -182,8 +186,17 @@ OPTIONS (call):
 
 OPTIONS (write):
    --rpc <rpcUrl>             RPC URL for the network
+   --fees <json>              Transaction fee options JSON passed to genlayer-js
+   --fee-value <wei>          Explicit fee deposit value
+   --valid-until <timestamp>  Unix timestamp after which the transaction is invalid
    --args <args...>           Method arguments (see Argument Types below)
 
+OPTIONS (estimate-fees):
+   --rpc <rpcUrl>             RPC URL for the network
+   --fees <json>              Fee estimate options JSON, or a transaction fee object
+   --include-report           Include simulation fee accounting/report in the generated estimate output
+   --args <args...>           Method arguments for simulation-derived estimates
+
 OPTIONS (schema):
    --rpc <rpcUrl>             RPC URL for the network
 
@@ -191,14 +204,51 @@ EXAMPLES:
    genlayer deploy
    genlayer deploy --contract ./my_contract.gpy
    genlayer deploy --contract ./my_contract.gpy --args "arg1" "arg2" 123
+   genlayer deploy --contract ./my_contract.gpy --fees '{"distribution":{"leaderTimeunitsAllocation":"100","validatorTimeunitsAllocation":"200","rotations":["0"]}}'
    genlayer call 0x123456789abcdef greet --args "Hello World!"
    genlayer write 0x123456789abcdef updateValue --args 42
+   genlayer write 0x123456789abcdef updateValue --fees '{"distribution":{"leaderTimeunitsAllocation":"100","validatorTimeunitsAllocation":"200","rotations":["0"]}}' --args 42
+   genlayer estimate-fees
+   genlayer estimate-fees 0x123456789abcdef updateValue --args 42
    genlayer write 0x123456789abcdef sendReward --args 0x6857Ed54CbafaA74Fc0357145eC0ee1536ca45A0
    genlayer write 0x123456789abcdef setScores --args '[1, 2, 3]'
    genlayer write 0x123456789abcdef setConfig --args '{"timeout": 30, "retries": 5}'
    genlayer schema 0x123456789abcdef
 ```
 
+##### Transaction Fee Options
+
+`--fees` accepts the same transaction fee object as `genlayer-js`. Quote large
+integer values as strings to preserve precision. `messageAllocations[].messageType`
+may be `"internal"`, `"external"`, `0`, or `1`.
+
+For targeted message budgets, the CLI can derive GenVM call keys before passing
+the JSON to `genlayer-js`:
+
+```bash
+genlayer estimate-fees 0x123456789abcdef settle \
+  --fees '{"messageAllocations":[{"messageType":"internal","recipient":"0x0000000000000000000000000000000000000001","callKeyMethod":"settle_campaign","budget":"700000"}]}'
+
+genlayer write 0x123456789abcdef sendReward \
+  --fees '{"messageAllocations":[{"messageType":"external","recipient":"0x0000000000000000000000000000000000000002","callKeySelector":"0xa9059cbb","budget":"210000"}]}'
+```
+
+Use `callKeyMethod` for internal GenVM messages, `callKeySelector` for a 4-byte
+EVM selector, or `callKeyCalldata` for full external calldata. Explicit
+`callKey` is still accepted for advanced cases.
+
+If `--fees` includes a `distribution` and `--fee-value` is omitted, the SDK
+derives the fee deposit from FeeManager on network backends, or from
+`sim_getFeeConfig` on Studio. Use `--fee-value` only when you need to force an
+explicit deposit value.
+
+`estimate-fees` prints the SDK fee preset. Without a contract/method it calls
+`estimateTransactionFees`. With a contract/method it uses the SDK target-write
+estimation helper so the preset reflects the observed Studio fee accounting
+report. Add `--include-report` to use the explicit simulate-and-derive path and
+include the simulation fee accounting and execution fee report next to the
+preset for reproducible gas-unit debugging.
+
 ##### Argument Types
 
 The `--args` option automatically detects and converts values to the correct type:
@@ -522,4 +572,3 @@ We welcome contributions to GenLayerJS SDK! Whether it's new features, improved
 ## License
 
 This project is licensed under the ... License - see the [LICENSE](LICENSE) file for details.
-