Skip to content

ci(workflows): sync e2e.yml from genlayer-e2e - #174

Merged
MuncleUscles merged 1 commit into
v1from
ci/sync-e2e-pipeline-v1
May 26, 2026
Merged

MuncleUscles merged 1 commit into
v1from
ci/sync-e2e-pipeline-v1

Conversation

@ci-core-e2e-runner

Copy link
Copy Markdown
Contributor

Description

Automated sync of .github/workflows/e2e.yml from the latest templates/e2e.yml in genlayer-e2e.

Review the diff and merge when ready. This PR was opened automatically when the template changed.

Release Notes

  • No user-facing changes (CI infrastructure only)

Types of Changes

  • CI/infrastructure change (non-breaking)
  • Bug fix
  • New feature
  • Breaking change

Checklist

  • Code follows project conventions
  • Documentation updated (if needed)
  • Changes tested locally (if applicable)

@MuncleUscles
MuncleUscles merged commit 71175f7 into v1 May 26, 2026
3 checks passed
@MuncleUscles
MuncleUscles deleted the ci/sync-e2e-pipeline-v1 branch May 26, 2026 19:24
MuncleUscles added a commit that referenced this pull request Jun 8, 2026
* Release v1.1.7 [skip ci]

* ci: scope down release/sync-docs to dedicated GitHub Apps (#168)

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.

* fix(ci): add trigger comment to publish workflow (#170)

No-op patch release to verify the publish pipeline end-to-end after
the env scope-down (#168) and npm trusted publisher update.

* Release v1.1.8 [skip ci]

* feat: branch-per-major release model (#172)

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 (#173)

* fix: run CI on v1 branch

* fix: sync testnet consensus abi

* ci(workflows): sync e2e.yml from genlayer-e2e (#174)

Co-authored-by: ci-core-e2e-runner[bot] <263344042+ci-core-e2e-runner[bot]@users.noreply.github.com>

* ci(workflows): sync e2e-housekeeper.yml from genlayer-e2e (#175)

Co-authored-by: ci-core-e2e-runner[bot] <263344042+ci-core-e2e-runner[bot]@users.noreply.github.com>

* ci(workflows): sync e2e.yml from genlayer-e2e (#176)

Co-authored-by: ci-core-e2e-runner[bot] <263344042+ci-core-e2e-runner[bot]@users.noreply.github.com>

* ci(workflows): sync e2e-housekeeper.yml from genlayer-e2e (#177)

Co-authored-by: ci-core-e2e-runner[bot] <263344042+ci-core-e2e-runner[bot]@users.noreply.github.com>

* feat: add v0.6 fee-aware transactions

* fix: handle studio raw transaction hashes

* fix: align studio fee floor fallback

* fix: satisfy fee estimate typecheck

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@genlayer.com>
Co-authored-by: Rafał Rabenda <99408377+rrabenda@users.noreply.github.com>
Co-authored-by: ci-core-e2e-runner[bot] <263344042+ci-core-e2e-runner[bot]@users.noreply.github.com>
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.

1 participant