Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
53 commits
Select commit Hold shift + click to select a range
a1c96f7
kona-node: Serve the system config lookup from imported blocks (#22466)
sebastianst Aug 21, 2026
6085f00
kona-host: harden online preimage fetching (#22604)
wwared Aug 21, 2026
e982ee6
kona-sp1: retain admitted proof request ownership (#22627)
digorithm Aug 21, 2026
052a3da
kona-protocol: Add a hash-keyed L2BlockInfo lookup for the reset walk…
sebastianst Aug 22, 2026
7ca2da1
kona!: remove op-supervisor-era interop legacy (#22552)
sebastianst Aug 22, 2026
07bc020
docs: extend the deletion review guide with build-metadata fallout (#…
sebastianst Aug 22, 2026
8f3cd3e
kona-interop: consolidate message validity rules (#22565)
claude[bot] Aug 23, 2026
4331ba5
release-notes: add skill for drafting house-style release notes (#22548)
geoknee Aug 23, 2026
ddff705
ci: bump rust nightly pin to nightly-2026-08-22 (#22650)
opgitgovernance Aug 23, 2026
4f5a6ec
op-deployer: set the default genesis time offset to 3H (#22512)
0xiamflux Aug 24, 2026
9104d73
docs: add node101 to OP Stack RPC directory (#22556)
girginomer10 Aug 24, 2026
d41f9e6
alloy-op-evm: regression-test dropped-tx SDM policy-touch rollback (#…
nonsense Aug 24, 2026
fabfc38
kona-node-service: support multiple chains in the L1 watcher (#22567)
claude[bot] Aug 25, 2026
382a79a
kona-gossip: Allowlist gossip subscription topics (#22661)
ajsutton Aug 26, 2026
68b0094
kona: make proof replay warnings actionable (#22623)
Inphi Aug 26, 2026
e199d0f
op-services: Update op-geth to v1.101702.3-rc.7 (#22694)
geoknee Aug 28, 2026
40ce66b
mise: Update bun to 1.4.0 (#22697)
ajsutton Aug 28, 2026
2258ea5
Update release docs: add proxyd v4.31.0 and v4.32.0 (#22695)
mintlify[bot] Aug 28, 2026
fc4ddf6
kona-sp1: raise SPN auction defaults so requests draw bids (#22640)
pauldowman Aug 31, 2026
6ea100a
contracts-bedrock: Super ZK Dispute Game Internal Review Remediations…
0xarktos Aug 31, 2026
19214e8
op-challenger: read interop game inputs status from superroot_atTimes…
pauldowman Aug 31, 2026
3caf10d
op-service: move PathFlag to a leaf package so oppprof is importable …
geoknee Sep 1, 2026
fda11cc
claude,docs: Add create-pr skill and consolidate PR guidance (#22608)
ajsutton Sep 1, 2026
7774a2d
ci: bump circleci-utils orb to 1.0.31 (stale-PR close-timing fix) (#2…
claude[bot] Sep 1, 2026
22e6fa4
docs: add SolidRPC to RPC directory (#22710)
DamianFigiel Sep 1, 2026
7103e9d
CODEOWNERS,public-docs: add monorepo-reviewers as co-owner of public …
claude[bot] Sep 1, 2026
1657fbe
kona-sp1: retain proving progress across retries (#22717)
digorithm Sep 1, 2026
f34bce2
op-challenger: fix interop vm runner picking an unusable game L1 head…
pauldowman Sep 1, 2026
9f70758
contracts-bedrock: Add missing StandardValidator assertions (#22471)
ajsutton Sep 1, 2026
9fa9979
derive: reserve Lagoon upgrade gas independently of the dependency se…
sebastianst Sep 2, 2026
98469b6
public-docs: fix high severity dependency alerts (#22733)
falcorocks Sep 2, 2026
cf871a7
rust: remove vulnerable libp2p paths (#22714)
falcorocks Sep 2, 2026
4d15b82
rust: allow the libp2p git source in cargo-deny (#22737)
claude[bot] Sep 2, 2026
a73fb22
op-core,op-node,op-batcher,op-service: shrink the set of packages emb…
sebastianst Sep 2, 2026
17e94f9
kona-sp1-proposer: right-size SPN submission parameters (#22741)
wwared Sep 2, 2026
4a44e56
kona-client: Skip consolidation when interop is inactive (#22730)
ajsutton Sep 2, 2026
fb4aada
kona/tests/proofs: migrate action tests to the interop client program…
OptimismBot Sep 2, 2026
5c631b7
op-challenger: record a stuck VM run as a timeout, not a setup failur…
OptimismBot Sep 3, 2026
3ac1beb
docs: Correct the Kona interop prestate type (#22746)
ajsutton Sep 3, 2026
d31eb17
public-docs: drop unused wallet connector dependency subtree (#22736)
falcorocks Sep 3, 2026
eea9542
security: Update module golang.org/x/crypto to v0.56.0 [SECURITY] (#2…
oplabs-renovate[bot] Sep 3, 2026
a8a3b81
kona-genesis: Add the genesis offset to the block number from a times…
ajsutton Sep 3, 2026
35f8fb9
docs: update flashblocks spec links to subblocks (#22755)
bitwiseguy Sep 3, 2026
29bec1e
kona-sp1-proposer: raise range split ceiling to 128 (#22762)
wwared Sep 3, 2026
e907fe5
kona-sp1: extract observable proposer cycle (#22503)
Inphi Sep 3, 2026
6a8e9c2
kona-sp1: make proposer task IDs nonzero (#22769)
Inphi Sep 3, 2026
5e4de61
justfile: refactor `release-notes` to add `release-paths` which can b…
pauldowman Sep 3, 2026
9cefc2f
docs: correct stale statuses in the op-geth decoupling doc and add do…
geoknee Sep 4, 2026
85f7c13
op-alloy,op-reth,kona: reject non-canonical transaction encodings (#2…
nonsense Sep 4, 2026
c6f3918
gitignore: ignore all rust target* dirs (#22779)
sebastianst Sep 4, 2026
b60a1a6
ci,contracts-bedrock: fail fast on unreachable apt indexes and drop t…
claude[bot] Sep 4, 2026
fca4f2e
Merge upstream op-reth/v2.4.3 into the Firehose line
sduchesneau Sep 11, 2026
deee61c
Record the op-reth v2.4.3 bump in the SF changelog and notes
sduchesneau Sep 11, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .circleci/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ parameters:

orbs:
continuation: circleci/continuation@2.0.1
utils: ethereum-optimism/circleci-utils@1.0.30
utils: ethereum-optimism/circleci-utils@1.0.31

jobs:
# --------------------------------------------------------------------------
Expand Down
4 changes: 1 addition & 3 deletions .circleci/continue/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ parameters:
default: false

orbs:
utils: ethereum-optimism/circleci-utils@1.0.30
utils: ethereum-optimism/circleci-utils@1.0.31
go: circleci/go@1.8.0
gcp-cli: circleci/gcp-cli@3.0.1
slack: circleci/slack@6.0.0
Expand Down Expand Up @@ -1200,8 +1200,6 @@ jobs:
name: Print forge version
command: forge --version
working_directory: packages/contracts-bedrock
- apt-install:
packages: "lcov"
- run:
name: Resolve L1 archive RPC URL
command: |
Expand Down
2 changes: 1 addition & 1 deletion .circleci/continue/rust-ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ version: 2.1
# This file contains all Rust CI commands, parameterized jobs, crate-specific jobs, and workflows.

orbs:
utils: ethereum-optimism/circleci-utils@1.0.30
utils: ethereum-optimism/circleci-utils@1.0.31
gcp-cli: circleci/gcp-cli@3.0.1

parameters:
Expand Down
2 changes: 1 addition & 1 deletion .circleci/continue/rust-e2e.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ version: 2.1
# It is merged with main.yml and rust-ci.yml when rust/** changes are detected.
# Shared orbs, commands, and jobs come from main.yml and rust-ci.yml during merge.
orbs:
utils: ethereum-optimism/circleci-utils@1.0.30
utils: ethereum-optimism/circleci-utils@1.0.31

parameters:
c-default_docker_image:
Expand Down
2 changes: 1 addition & 1 deletion .circleci/scripts/apt-install.sh
Original file line number Diff line number Diff line change
Expand Up @@ -20,5 +20,5 @@ APT_OPTS=(-o Acquire::Retries=3 -o Acquire::http::Timeout=20 -o Acquire::https::
export NEEDRESTART_MODE=a
export DEBIAN_FRONTEND=noninteractive

sudo -E apt-get "${APT_OPTS[@]}" update
sudo -E apt-get "${APT_OPTS[@]}" update --error-on=any
sudo -E apt-get "${APT_OPTS[@]}" install -y "$@"
12 changes: 12 additions & 0 deletions .claude/skills/create-pr/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
---
name: create-pr
description: Open a pull request in the Optimism monorepo after you commit the change locally — run the review agents that apply to the diff, test, rebase, write a description that gives the reason for the change, create the PR, then watch CI. Use when asked to open, create, raise, or submit a PR, or to push a branch for review.
---

# Create a PR

[docs/handbook/pr-guidelines.md](../../../docs/handbook/pr-guidelines.md) is the source of
truth for the steps — review agents, tests, rebase, title, description, and CI. Read it and
follow it in order. This file applies after you commit the change on a feature branch.

Run the review agents as parallel subagents, so their output stays out of your context.
147 changes: 147 additions & 0 deletions .claude/skills/release-notes/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,147 @@
---
name: release-notes
description: Write the release notes for an OP Stack component using the house style. Use when asked to write, polish, tidy, or finalize release notes, to clean up a draft GitHub release, or to prepare notes before publishing a release.
---

# Release notes

`just release-notes <component>` emits a git-cliff changelog: every PR whose diff hit the
component's include paths, as a flat list of PR titles. A published note is a different
artifact — a **curated change list**, grouped by theme, where each entry explains itself and
only changes that reach the binary appear at all.

The raw list is replaced, not annotated. Read `reference/house-style.md` before writing and
`reference/triage.md` before pruning.

This skill does not create or finalize tags.

## 1. Establish the target

Ask which component and which release, unless the user already said.

```bash
gh release list --limit 20 # 'Draft' rows are the candidates
```

**Check for both an RC and a finalized draft of the same version.** Release automation
creates a fresh draft when an RC is finalized, and that finalized draft is the one that gets
published. If both exist, target the finalized one and say so.

## 2. Get the draft

```bash
gh release view <tag> --json body -q .body > /tmp/<component>-draft.md
```

If there is no draft yet:

```bash
GITHUB_TOKEN=$(gh auth token) just release-notes <component> # latest stable -> latest RC
GITHUB_TOKEN=$(gh auth token) just release-notes <component> latest develop
```

More than one `## What's Changed in ...` section means earlier RCs were never published.
Merge them under the final tag and dedupe by PR number.

## 3. Find out what each PR actually touched

```bash
.claude/skills/release-notes/scripts/pr-facts.sh /tmp/<component>-draft.md <component>
```

Each PR is tagged `LINKED` (changed a package compiled into the binary, and which ones),
`DEPS` (manifests only), `--` (nothing the binary compiles) or `?` (unresolvable). The tags
come from `go list -deps` and `cargo tree`, so linkage is exact — but it proves the package
is compiled in, not that the changed function is on the component's runtime path.

## 4. Triage

Drop `--` and non-security `DEPS` rows, then apply the judgment pass in
`reference/triage.md` to every `LINKED` row.

Read the intent of each surviving PR — you cannot write a self-contained entry from a title.
Batch the lookups; if there are more than ~15, delegate the reading and ask for a one-line
"what an operator would notice" per PR.

Keep the raw bullets for cut PRs as HTML comments at the bottom of the draft, each with a
short reason, so a reviewer can reinstate one in a single edit.

## 5. Curate the change list

The substance of the job. Replace PR titles with grouped, self-contained entries:

- group under `### Features` / `### Bug fixes` / `### Other`, or by domain; drop empty
headings, and use a flat list for a short release
- fold PRs that are one logical change into one entry carrying all their numbers
- **write impact, never implementation** — the symptom that appears or disappears, the
flag/metric/config names, what the reader must do. Not goroutines, event loops, call
paths, internal type names, or which PR was stacked on which. This is the correction made
most often, and the PR descriptions you just read will pull you the wrong way
- omit pure internal churn entirely
- reference PRs as bare `(#NNNNN)`; no `by @author`
- only mention a PR more than once if it included multiple logical changes which are worth describing separately

## 6. Write the Overview

One callout at the top of `## Overview`: release type, what it contains, and one of
`optional` / `optional but recommended` / `recommended` / `required`, scopable to a role.
Always `> [!NOTE]`, except `required`, which uses `> [!CAUTION]`.

Then check proportionality:

- **Is the feature live?** Verify with the registry check in `reference/house-style.md`
rather than assuming; ask the release manager for anything not expressed as a hardfork. A
dormant-path change that is a no-op for this component gets cut; one that will matter on
activation gets a line under a `### <Feature> (not yet in production)` heading. Either
way, do not describe an attack the live system cannot suffer.
- **Would a reader shrug?** New metrics, a wrong version string and rare corner cases are
bullets, not callouts.

Add `## Breaking changes` only when an operator must *do* something before upgrading;
Go-API-only changes do not qualify. The Overview block is the note's only callout.

## 7. Assemble

Order: `## Overview` → optional `## Breaking changes` → `## What's Changed` with its
subheadings → `**Full Changelog**` → image line → commented-out working notes. Write to
`/tmp/<component>-notes.md`.

## 8. Retarget RC references when finalizing

A draft generated against an RC carries `-rc.N` in its heading, compare link and image tag.
Publishing that finalized points operators at an RC image.

```bash
.claude/skills/release-notes/scripts/retarget-tag.sh /tmp/<component>-notes.md <component>
```

It **refuses**, leaving the file untouched, if the finalized tag is missing or sits on a
different commit than the RC. Surface that warning rather than editing by hand — a note
generated for a different commit needs regenerating, not retagging.

Then set the compare link's base to the previous **finalized** tag.

## 9. Review before applying

**[USER REVIEW]** Show the proposed notes in full **and the drop list** — every pruned PR
with its tag and a few words on why. A wrongly pruned PR is invisible in the rendered note,
so present it as a list to check.

## 10. Apply

Only after explicit approval:

```bash
gh release edit <tag> --notes-file /tmp/<component>-notes.md
```

This changes only the body, leaving draft/published state alone. Confirm with
`gh release view <tag>` and report what changed.

## Notes

- A change under `op-service/` or `op-core/` can change a component's behaviour. Never prune
on directory name alone; that is what step 3 is for.
- Check a judgment call against history by examining recent releases for the same component.
- Never overwrite a draft a human has curated. If the body carries hand-written prose or
commented-out bullets, propose specific edits instead of replacing it.
Loading
Loading