fix(L1): bump SystemConfig semver for the ETHLockbox removal

[jackchuma]

Summary

#439 bumped OptimismPortal2, DisputeGameFactory and AggregateVerifier on the grounds that each "[has] source changes relative to the versions currently deployed onchain, but still declare the same semver." SystemConfig meets that same description and was missed, so this bumps it 3.13.2 -> 3.14.0.

Why it qualifies

#378 (ETHLockbox removal) changed SystemConfig behaviour without touching the version:

-        address identifier = isFeatureEnabled[Features.ETH_LOCKBOX]
-            ? address(IOptimismPortal2(payable(optimismPortal())).ethLockbox())
-            : address(optimismPortal());
-        return superchainConfig.paused(address(0)) || superchainConfig.paused(identifier);
+        return superchainConfig.paused(address(0)) || superchainConfig.paused(optimismPortal());

• paused() no longer selects the pause identifier based on whether the ETH_LOCKBOX feature is enabled.
• _setFeature no longer guards ETH_LOCKBOX against being disabled while the portal still has a lockbox configured, or toggled while the system is paused.

snapshots/semver-lock.json already recorded the divergence. Comparing 1baa168c (the commit Base's Zeronet SystemConfig implementation was built from) against main:

	1baa168c	main
sourceCodeHash	0x1a24ffe1…	0x780ff372…
initCodeHash	0x3e8e52d9…	0xb91123c7…
@custom:semver	3.13.2	3.13.2

So the lock file and the declared version disagreed: the contract changed, the version did not.

Why minor, not major

No function, error or event declarations were added or removed, so the ABI is unchanged. That matches the DisputeGameFactory 1.4.0 -> 1.5.0 precedent in #439. OptimismPortal2 went major there only because it dropped ethLockbox() from its ABI.

Impact

Without this, a chain upgraded for Cobalt reports an unchanged SystemConfig version, so version() cannot distinguish the pre- and post-upgrade implementations and operators have to fall back to comparing implementation addresses. This surfaced while preparing the Zeronet Cobalt upgrade in contract-deployments#790, where the facilitator guide currently has to call out SystemConfig as a special case for exactly this reason.

Testing

• just semver-lock regenerated; only the SystemConfig entry moves.
• just snapshots produces no further changes, so no ABI or storage snapshot is affected.
• just test: 1231 passed, 0 failed, 1 skipped.

A backport to releases/v8.3.0 follows separately.

Made with Cursor

[cb-heimdall]

✅ Heimdall Review Status

Requirement	Status	More Info
Reviews	✅ 1/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1