chore: update translation progress from Crowdin [skip ci]
May 27, 6-7 AM (49)
May 27, 7-8 AM (65)
May 27, 8-9 AM (38)
May 27, 9-10 AM (74)
May 27, 10-11 AM (83)
May 27, 11-12 PM (30)
May 27, 12-1 PM (50)
May 27, 1-2 PM (39)
May 27, 2-3 PM (53)
May 27, 3-4 PM (37)
May 27, 4-5 PM (11)
May 27, 5-6 PM (18)
May 27, 6-7 PM (21)
May 27, 7-8 PM (25)
May 27, 8-9 PM (19)
May 27, 9-10 PM (15)
May 27, 10-11 PM (29)
May 27, 11-12 AM (27)
May 28, 12-1 AM (9)
May 28, 1-2 AM (3)
May 28, 2-3 AM (5)
May 28, 3-4 AM (2)
May 28, 4-5 AM (9)
May 28, 5-6 AM (34)
May 28, 6-7 AM (31)
May 28, 7-8 AM (84)
May 28, 8-9 AM (33)
May 28, 9-10 AM (54)
May 28, 10-11 AM (50)
May 28, 11-12 PM (21)
May 28, 12-1 PM (47)
May 28, 1-2 PM (50)
May 28, 2-3 PM (23)
May 28, 3-4 PM (43)
May 28, 4-5 PM (86)
May 28, 5-6 PM (13)
May 28, 6-7 PM (31)
May 28, 7-8 PM (43)
May 28, 8-9 PM (34)
May 28, 9-10 PM (17)
May 28, 10-11 PM (36)
May 28, 11-12 AM (32)
May 29, 12-1 AM (12)
May 29, 1-2 AM (13)
May 29, 2-3 AM (4)
May 29, 3-4 AM (3)
May 29, 4-5 AM (0)
May 29, 5-6 AM (2)
May 29, 6-7 AM (5)
May 29, 7-8 AM (16)
May 29, 8-9 AM (37)
May 29, 9-10 AM (34)
May 29, 10-11 AM (69)
May 29, 11-12 PM (25)
May 29, 12-1 PM (44)
May 29, 1-2 PM (66)
May 29, 2-3 PM (61)
May 29, 3-4 PM (26)
May 29, 4-5 PM (26)
May 29, 5-6 PM (83)
May 29, 6-7 PM (11)
May 29, 7-8 PM (19)
May 29, 8-9 PM (15)
May 29, 9-10 PM (9)
May 29, 10-11 PM (27)
May 29, 11-12 AM (7)
May 30, 12-1 AM (9)
May 30, 1-2 AM (2)
May 30, 2-3 AM (1)
May 30, 3-4 AM (7)
May 30, 4-5 AM (2)
May 30, 5-6 AM (11)
May 30, 6-7 AM (0)
May 30, 7-8 AM (2)
May 30, 8-9 AM (11)
May 30, 9-10 AM (13)
May 30, 10-11 AM (10)
May 30, 11-12 PM (5)
May 30, 12-1 PM (8)
May 30, 1-2 PM (5)
May 30, 2-3 PM (18)
May 30, 3-4 PM (5)
May 30, 4-5 PM (1)
May 30, 5-6 PM (9)
May 30, 6-7 PM (9)
May 30, 7-8 PM (1)
May 30, 8-9 PM (5)
May 30, 9-10 PM (4)
May 30, 10-11 PM (27)
May 30, 11-12 AM (12)
May 31, 12-1 AM (17)
May 31, 1-2 AM (0)
May 31, 2-3 AM (1)
May 31, 3-4 AM (1)
May 31, 4-5 AM (0)
May 31, 5-6 AM (0)
May 31, 6-7 AM (7)
May 31, 7-8 AM (4)
May 31, 8-9 AM (10)
May 31, 9-10 AM (3)
May 31, 10-11 AM (4)
May 31, 11-12 PM (4)
May 31, 12-1 PM (1)
May 31, 1-2 PM (2)
May 31, 2-3 PM (24)
May 31, 3-4 PM (16)
May 31, 4-5 PM (2)
May 31, 5-6 PM (1)
May 31, 6-7 PM (2)
May 31, 7-8 PM (2)
May 31, 8-9 PM (2)
May 31, 9-10 PM (7)
May 31, 10-11 PM (25)
May 31, 11-12 AM (11)
Jun 01, 12-1 AM (14)
Jun 01, 1-2 AM (7)
Jun 01, 2-3 AM (3)
Jun 01, 3-4 AM (10)
Jun 01, 4-5 AM (13)
Jun 01, 5-6 AM (16)
Jun 01, 6-7 AM (10)
Jun 01, 7-8 AM (14)
Jun 01, 8-9 AM (46)
Jun 01, 9-10 AM (50)
Jun 01, 10-11 AM (19)
Jun 01, 11-12 PM (27)
Jun 01, 12-1 PM (49)
Jun 01, 1-2 PM (40)
Jun 01, 2-3 PM (44)
Jun 01, 3-4 PM (34)
Jun 01, 4-5 PM (54)
Jun 01, 5-6 PM (5)
Jun 01, 6-7 PM (32)
Jun 01, 7-8 PM (37)
Jun 01, 8-9 PM (9)
Jun 01, 9-10 PM (12)
Jun 01, 10-11 PM (30)
Jun 01, 11-12 AM (22)
Jun 02, 12-1 AM (13)
Jun 02, 1-2 AM (8)
Jun 02, 2-3 AM (5)
Jun 02, 3-4 AM (14)
Jun 02, 4-5 AM (10)
Jun 02, 5-6 AM (43)
Jun 02, 6-7 AM (32)
Jun 02, 7-8 AM (58)
Jun 02, 8-9 AM (65)
Jun 02, 9-10 AM (28)
Jun 02, 10-11 AM (19)
Jun 02, 11-12 PM (15)
Jun 02, 12-1 PM (47)
Jun 02, 1-2 PM (66)
Jun 02, 2-3 PM (97)
Jun 02, 3-4 PM (23)
Jun 02, 4-5 PM (15)
Jun 02, 5-6 PM (27)
Jun 02, 6-7 PM (29)
Jun 02, 7-8 PM (17)
Jun 02, 8-9 PM (9)
Jun 02, 9-10 PM (19)
Jun 02, 10-11 PM (33)
Jun 02, 11-12 AM (22)
Jun 03, 12-1 AM (13)
Jun 03, 1-2 AM (31)
Jun 03, 2-3 AM (16)
Jun 03, 3-4 AM (0)
Jun 03, 4-5 AM (7)
Jun 03, 5-6 AM (9)
Jun 03, 6-7 AM (3)
3,752 commits this week
May 27, 2026
-
Jun 03, 2026
ci(cardano-node): fix moog download for 0.5.x + alert on scheduled failure
The nightly scheduled run has failed at 'Install moog' every cron tick since moog 0.5.x dropped the moog-*-linux64.tar.gz asset (last green 2026-06-01). Replace the get-latest-release + release-downloader actions with a gh release download that picks the statically-linked moog-*-x86_64-linux-musl.tar.gz, filtering out the agent/oracle tarballs. Also add an 'Alert on scheduled failure' step (issues:write) that opens or appends to a single tracking issue, so a silently-failing nightly run becomes visible instead of rotting for days.
chore(gov): pin gov-cli to instrumented image for next run
feat(gov): mirror perturbation-coverage instrumentation (python)
Port the bash coverage assertions to the cardano-clusterlib drivers: anytime_chain_progress perturbation witness, gov_op_under_perturbation, action_voted_by_all_roles / action_majority_reached (with details), action_lifecycle_closed, committee_quorum_maintained, plus the set_chain_verdict/recent_stall helpers and sdk setup_complete + details.
feat(gov): perturbation-coverage instrumentation (bash)
Turn the Sometimes-assertion set into a real coverage scorecard: - anytime_chain_progress: perturbation witness — samples relay1's tip over a 20s window; chain_stalled_under_fault goes green only when faults actually halted block production, chain_producing when it recovers. Publishes a verdict the create/vote drivers read. - create/vote: gov_op_under_perturbation when an op lands during a stall. - vote: condition-bearing action_voted_by_all_roles + action_majority_ reached (with details), action_lifecycle_closed on vote rejection. - anytime_govstate: committee_quorum_maintained Always-invariant. - helper_sdk: sdk_setup_complete lifecycle helper. - helper_gov: set_chain_verdict / recent_stall. Adds components/gov-cli/INSTRUMENTATION.md documenting the full signal surface and how to read the coverage scorecard. Validated locally: condition-bearing Sometimes flip green only when the state is reached (majority at 6/6; all-roles once drep+spo+cc present).
Tee the logs when running against the testnet
chore: upgrade crate versions
* mithril-stm from `0.10.28` to `0.10.29`
Add an .envrc that uses the nix dev shell
Fix pin-config script and configs
Create config and instructions to run against the testnet
Merge pull request #92 from cardano-foundation/karknu/mempool_percent
Grafana improvements
Use o-c and ledger with staging area
chore(deps): bump actions/checkout from 6.0.2 to 6.0.3
Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.2 to 6.0.3. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/de0fac2e4500dabe0009e67214ff5f5447ce83dd...df4cb1c069e1874edd31b4311f1884172cec0e10) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Pass networkId to PState translation (Dijkstra)
v2: don't leak pkgsBuildBuild build-tool sources into cross slices
On cross, `buildToolSlices` are the build-build (pkgsBuildBuild) tool slices. They were added to `depSlices` -> `propagatedBuildInputs`, so the build-time slicing-repo composer walked their `repo-frag` (source tarball + index .cabal) into the cross slice's hackage repo, alongside the cross tool's repo-frag. cabal then saw two candidates for the tool (e.g. a build-build `hsc2hs-0.68.10` and the cross one); a dependent's build-tool exe-dep could resolve to the build-build unit, whose UnitId feeds the consumer's cross UnitId but never appears in its Setup configure args. That forked dependent unit-ids (e.g. network) away from what cabal computes elsewhere, so `checkAgainstPlan` failed in any slice depending on a build-tool-using package -- breaking the whole aarch64/armv7a-android-prebuilt suite (via iserv-proxy) and other cross targets. On cross the tool's cross store unit already comes from `transitiveBuildToolSlices` (the cross `targetSlice`) and its runnable binary from `buildToolBinOverlays` / `withProgFlags` (both reference `buildSlice` directly), so the build-build slices must stay out of `propagatedBuildInputs` here.
deploy: f017b7151459474675d0939199edafc5cc3b9dcf
feat(tray/notifications): multi-target monitoring engine + dispatch wizard
Adds a fyne-free notifications engine that derives one rule per (kind, param) from a multi-target SetupPlan (Wallets/DReps/Pools/ MonitorEverything) and emits Requests through a tumbling-window rate limiter; connection alerts bypass it. The wizard gains three editable target sections with cross-template validation hints, overwrites notify_prefs on Apply, and no longer blocks finishing on the macOS test notification. Removes tray/adder_config.go (dead code — only its own tests called it; the live SetupPlan→YAML path is setup/codec.go::ToEngineConfig). Implements #685 Signed-off-by: Ales Verbic <[email protected]>
test(txbuilder): harden determinism tests and drop redundant dev-deps
Address review feedback on the Conway build test harness: - Strengthen multi_asset_output_is_deterministic / mint_is_deterministic to assert a single unique encoding across 64 fresh builds (collected into a HashSet) and to stage two asset names under one policy, so both the outer (policy) and inner (asset-name) BTreeMap sorts are exercised. Each build constructs a fresh, per-instance re-seeded HashMap, which is what drives the pre-encode order variation; the previous form compared one fixed-order build to itself and never varied the bundle order. - Assert bundle sizes in output_asset_value_round_trips and mint_and_burn_round_trip so a spuriously added asset/policy cannot slip past the single-entry .next() checks. - Reword the script_data_hash_matches_recomputation doc comment to make clear it is a self-consistency check, not a cross-check against cardano-cli (it reuses the builder's legacy list-form redeemer encoding). - Remove the [dev-dependencies] block from pallas-txbuilder/Cargo.toml: pallas-crypto, pallas-primitives, pallas-addresses, and hex are all already in [dependencies], which Cargo makes available to integration tests. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
chore(deps): Bump google.golang.org/api from 0.282.0 to 0.283.0
Bumps [google.golang.org/api](https://github.com/googleapis/google-api-go-client) from 0.282.0 to 0.283.0. - [Release notes](https://github.com/googleapis/google-api-go-client/releases) - [Changelog](https://github.com/googleapis/google-api-go-client/blob/main/CHANGES.md) - [Commits](https://github.com/googleapis/google-api-go-client/compare/v0.282.0...v0.283.0) --- updated-dependencies: - dependency-name: google.golang.org/api dependency-version: 0.283.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
chore(deps): Bump cloud.google.com/go/secretmanager
Bumps [cloud.google.com/go/secretmanager](https://github.com/googleapis/google-cloud-go) from 1.16.0 to 1.20.0. - [Release notes](https://github.com/googleapis/google-cloud-go/releases) - [Changelog](https://github.com/googleapis/google-cloud-go/blob/main/documentai/CHANGES.md) - [Commits](https://github.com/googleapis/google-cloud-go/compare/kms/v1.16.0...dlp/v1.20.0) --- updated-dependencies: - dependency-name: cloud.google.com/go/secretmanager dependency-version: 1.20.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
chore(deps): Bump modernc.org/sqlite from 1.44.3 to 1.51.0
Bumps [modernc.org/sqlite](https://gitlab.com/cznic/sqlite) from 1.44.3 to 1.51.0. - [Changelog](https://gitlab.com/cznic/sqlite/blob/master/CHANGELOG.md) - [Commits](https://gitlab.com/cznic/sqlite/compare/v1.44.3...v1.51.0) --- updated-dependencies: - dependency-name: modernc.org/sqlite dependency-version: 1.51.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>