Repository navigation
Conversation
…platform/local-ydb The Yandex Container Registry image's version tags stop at 23.3/trunk with no numbered releases since 2023, and there is no `latest`. The Go/Python/Java/.NET/Rust/Node.js reference SDKs all test against ydbplatform/local-ydb instead, which is actively updated (`latest` is currently a real 26.1.1.22 build) and offers a continuous range of numbered tags. Verified live that binary paths, default database (/local), default ports (2135/2136/8765), and default TLS cert path (/ydb_certs) are unchanged, so no other service config was needed. Dropped YDB_USE_IN_MEMORY_PDISKS, which this image doesn't read.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #292 +/- ##
=========================================
Coverage 52.67% 52.67%
Complexity 989 989
=========================================
Files 66 66
Lines 2690 2690
=========================================
Hits 1417 1417
Misses 1273 1273
🚀 New features to boost your workflow:
|
SELECT version() exists from 24.3 (24.1 and older reject it as an unknown builtin) and every matrix entry is 24.4+, so query it in a step and export the result as YDB_VERSION for later steps, instead of leaving the matrix tag (latest/edge/trunk) as the only hint about the server. The value is not always numeric: 24.4 -> 24.4.4.12, 25.4 -> stable-25-4-1, latest -> 26.1.1.22, edge -> 26.3.1.17, trunk -> main. Checked against each image.
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
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.
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
The CI service image is pulled from
cr.yandex/yc/yandex-docker-local-ydb. That registry's numbered release tags stop at23.3(2023) and it has nolatesttag, so the matrix (['stable-22-5', 'trunk', '23.3', '23.2', '23.1']) only exercises 2022-2023 snapshots plus one bleeding-edgetrunkbuild - no released 24.x/25.x/26.x version is covered.Issue Number: #293
What is the new behavior?
ydbplatform/local-ydb, the image already used by the Go/Python/Java/.NET/Rust/Node.js SDKs' own CI, which is actively updated (latestis currently a real26.1.1.22build).['24.4', '25.4', 'latest', 'edge', 'trunk'].YDB_USE_IN_MEMORY_PDISKS, which this image doesn't read.Other information
Verified live that binary paths (
/ydbd,/ydb), default database (/local), default ports (2135/2136/8765) and default TLS cert path (/ydb_certs) are unchanged between the two images, so no other service config needed to change.