Skip to content

feat(fees): integrate v0.6 tooling - #180

Merged
MuncleUscles merged 15 commits into
v2-devfrom
codex/v06-fees-tooling
Jun 8, 2026
Merged

MuncleUscles merged 15 commits into
v2-devfrom
codex/v06-fees-tooling

Conversation

@MuncleUscles

@MuncleUscles MuncleUscles commented Jun 2, 2026 •

Copy link
Copy Markdown
Member

Summary

  • opens the actual genlayer-js fee integration on the v2 development line
  • adds fee-aware transaction types/helpers and v0.6 chain metadata needed by the tooling train
  • keeps this as a draft while cross-repo e2e is wired and expected failures are surfaced

Notes

This PR is for triggering and gating the v0.6 fee train. It should not be merged until the Studio-backed tooling e2e run is green and the broader release train is ready.

Other component refs should come from the central v0.6 matrix unless a specific cross-repo PR needs to be tested.

Depends-On: genlayerlabs/genlayer-py#88
Depends-On: genlayerlabs/genlayer-testing-suite#90

github-actions[bot] and others added 11 commits April 25, 2026 11:02
Replace the over-privileged shared CI bot with two dedicated, minimally
scoped GitHub Apps gated behind protected environments. Mirrors the
same change in genlayer-testing-suite#78 and genlayer-cli#297.

- publish.yml: rename environment npm -> Publish, switch from
  tibdex/github-app-token@v1 (archived) to actions/create-github-app-token@v3
  with vars.PUBLISH_CI_APP_CLIENT_ID + secrets.PUBLISH_CI_APP_KEY.
- sync-docs.yml: bump create-github-app-token to @V3, switch to
  client-id, gate behind the Sync-docs environment with
  vars.DOCS_SYNC_APP_CLIENT_ID + secrets.DOCS_SYNC_APP_KEY.

Each App should be installed only on the repos it needs (Publish: this
repo only; Sync-docs: this repo + genlayer-docs) with Contents: read
& write as the only permission.
No-op patch release to verify the publish pipeline end-to-end after
the env scope-down (#168) and npm trusted publisher update.
Aligns this repo with genlayer-node + genvm: branches per major (v1
today; v2 / v2-dev when fees lands), no main, deliberate releases via
script + skill.

What changes:
- publish.yml fires on `push: tags v*` instead of `push: main`. The
  workflow no longer bumps versions — it just sanity-checks that the
  tag matches package.json, builds, publishes to npm, and creates the
  GitHub Release. No commits back to the branch.
- scripts/release.sh is the new release entry point. Pre-flight checks:
  on a v<major> branch, clean tree, in sync with origin, latest CI
  green. Refuses major bumps without --allow-major (those need a new
  branch in this model). Then runs release-it with an explicit
  version to bump package.json, prepend CHANGELOG.md, commit, tag,
  push — but with npm/github plugins disabled so the dev machine
  doesn't need npm auth and the GH release is cut by CI from the tag.
- .claude/skills/release/SKILL.md documents the flow for Claude: when
  to use it, what to confirm with the user, what to refuse, and the
  roll-back path (deprecate, never unpublish blind).
- CONTRIBUTING.md explains the branch model + points at the skill.
- npm run release → ./scripts/release.sh so the convenience script
  routes through pre-flight checks (the previous `release-it --ci`
  invocation bypassed every guard).
- .github/e2e-track on this branch points at runner track v0.5
  (current stable). v2-dev (when it exists) will point at v0.6-dev.

Why kill auto-bump:
- Twice landed accidental majors when a BREAKING CHANGE footer in a
  PR body triggered the conventional-commit bump algorithm — once on
  this repo (0.28.7 → 1.0.0), once on genlayer-testing-suite (yanked
  v1/v2 tags). The whatBump cap mitigated future jumps but didn't
  address the underlying issue: shipping a release shouldn't be a
  side-effect of merging a PR.
- The new flow puts a human checkpoint between "code lands" and
  "users get it" without losing the bump-and-tag automation.

Follow-up (separate PRs):
- After this lands: switch default branch on github.com from main to
  v1, then delete origin/main.
- Same shape applied to genlayer-py, genlayer-cli,
  genlayer-testing-suite, genlayer-explorer (per their existing major).
- Runner matrix updates: matrix/v0.5.yaml tooling refs switch from
  tag pins to branch pins (genlayer-js: v1).
* fix: run CI on v1 branch

* fix: sync testnet consensus abi
Co-authored-by: ci-core-e2e-runner[bot] <263344042+ci-core-e2e-runner[bot]@users.noreply.github.com>
Co-authored-by: ci-core-e2e-runner[bot] <263344042+ci-core-e2e-runner[bot]@users.noreply.github.com>
Co-authored-by: ci-core-e2e-runner[bot] <263344042+ci-core-e2e-runner[bot]@users.noreply.github.com>
Co-authored-by: ci-core-e2e-runner[bot] <263344042+ci-core-e2e-runner[bot]@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Jun 2, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2e6c63e7-5187-4d55-93ee-0c063d19594e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/v06-fees-tooling

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@MuncleUscles

Copy link
Copy Markdown
Member Author

/run-e2e v0.6 tooling studio

@MuncleUscles

Copy link
Copy Markdown
Member Author

/run-e2e

@MuncleUscles

Copy link
Copy Markdown
Member Author

/run-e2e v0.6 tooling studio cache-bust=app-proof-20260605-1

@MuncleUscles

Copy link
Copy Markdown
Member Author

/run-e2e v0.6 tooling studio cache-bust=app-proof-20260605-2

@MuncleUscles

Copy link
Copy Markdown
Member Author

/run-e2e v0.6 tooling studio cache-bust=app-proof-20260605-3

@ci-core-e2e-runner

Copy link
Copy Markdown
Contributor

/run-e2e v0.6 tooling studio cache-bust=py88-proof-20260605-1

@MuncleUscles

Copy link
Copy Markdown
Member Author

/run-e2e v0.6 tooling studio cache-bust=testing-suite90-20260605-1

@MuncleUscles
MuncleUscles marked this pull request as ready for review June 8, 2026 16:05
@MuncleUscles
MuncleUscles merged commit 75f90e2 into v2-dev Jun 8, 2026
3 checks passed
@MuncleUscles
MuncleUscles deleted the codex/v06-fees-tooling branch June 8, 2026 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants