release: v0.18.0 - #44
Merged
Merged
Conversation
Every module Dockerfile carries an optional COPY glob that only BuildKit accepts, so a host whose docker build fell to the legacy builder failed mid-install with an opaque COPY error. The install now probes for buildx before the build, names the missing docker-buildx-plugin, and pins DOCKER_BUILDKIT=1 for the build.
…ed on an unreadable migration count fix(node): clear the hub price-ingest fence per network now the schema carries it fix(node): refuse an unreadable migration table count instead of collapsing it into empty-database test(node): stub DbCredentialDrift so ModuleService unit tests never spawn docker chore(node): resync the vendored coin registry with the hub FULLNODE comment
A venue with no XCHAIN token record answers the explorer token lookup with a bare HTTP 404, which surfaced as an unexplained crash during `validator stake`. The lookup is now wrapped so a 404 becomes a message that names the missing gas token and points at the venue's gas-token bootstrap.
… pin The GAS_SCHEDULE comment still described the UNIFIED_FEES_SWEEP_CALLBACK keys as unarmed on both networks, which stopped being true when mainnet armed at genesis and testnet took an armed date. It now records the real per-network state and separates that from CONSENSUS_CONFIG_PIN.mainnet, which stays null for its own later arm.
…e shared alias Every coin node carries the docker alias `node`, and the indexer and hub containers sit on more than one coin network, so from those containers the alias resolved to whichever sibling network sorted first and a dogecoin stack's RPC credentials reached the bitcoin node. The container name is unique per coin and network and resolves on any network both containers share.
The smoke suite asserted on untracked per-coin config files and on an out-of-date `update` argument count, and two unit tests read this machine's validator directory and paid the SDK's first load inside a timed test. Each now describes a checkout with no local install state and skips what is not there.
Bumps the package and lockfile to 0.18.0 and dates the 0.18.0 changelog entry. The manifest, README badge and release notes are written separately from the tagged sibling SHAs.
Pins the eleven components this train tagged to their signed master merge commits and holds xchain-contracts at v0.17.0, which the sparse-lockstep rule leaves unbumped because it carries no commits since that train. The README version badge moves to 0.18.0; it was still reading 0.17.0 because the step 3 refresh derives the badge from the highest tag, which does not exist yet when that step runs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Node's carrier cut for the v0.18.0 train, opened last per the release ceremony so the manifest can pin tags that already exist.
src/release-manifest.jsonpins the eleven components this train tagged to their signed master merge commits, and holdsxchain-contractsat v0.17.0 under sparse lockstep because it carries no commits since that train. NotrainActivationblock: this is a MINOR train, so the fleet keeps resolving the 1.0.0 rule set.The e2e matrix ran green at
release/v0.18.0on all three coins, 326 per coin across the action, security and performance legs with zero failures.