Skip to content

v1.6.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 21:59
· 291 commits to main since this release
v1.6.0
a1c62be

The crate moves to dynoxide-rs 3.3.0, which adds public items and removes
none. Everything else a user installs carries 1.6.0. The release brings PartiQL
reads, request validation and number handling closer to DynamoDB, so some
requests answer differently: see Behaviour changes and
docs/compatibility-summary.md.

Security

  • zstd moves to 0.13.4, zstd-safe to 7.4.0 and zstd-sys to 2.1.2 for
    RUSTSEC-2026-0391, RUSTSEC-2026-0398, RUSTSEC-2026-0403 and
    RUSTSEC-2026-0410. They cover context reuse across streams, seekable and
    legacy-frame decompression, and the wasm32 allocator shim. Dynoxide only
    compresses import output with a fresh zstd::Encoder on native targets, so
    none of them reach its code, but zstd is built into the binary with the
    import feature, so it ships in this release.

Behaviour changes

  • Expressions refuse attribute names starting with _ unless they use an
    ExpressionAttributeNames alias
    , as DynamoDB does, in key condition,
    filter, projection, condition and update expressions alike. This includes
    an import rule's match expression, so a rule matching such an attribute
    now needs an alias in its names. A rule's path is unaffected
    (#274).
  • PartiQL reads one partition where DynamoDB does. A SELECT whose OR
    branches all name the same partition key, or whose sort key is matched with
    IN, now reads and charges only those keys, and Limit counts only their
    rows. These used to scan the table or read the whole partition, so their
    charges and page counts change. The entries under Fixed give the detail.

Fixed

  • An UpdateItem that creates its item returns no Attributes for
    ReturnValues: ALL_OLD, whether it uses SET, REMOVE or no update
    expression. It used to return the key attributes as the old image.
    Captured against eu-west-2 and us-east-1 on 5 November 2026
    (#278,
    #292, thanks
    @alfaproject).
  • A PartiQL SELECT on one partition refuses a NOT written over a key
    attribute inside an OR whose other branch names no key attribute, such as
    pk = 'k' AND (NOT sk = 's0' OR x = 0), with DynamoDB's Filter Expression can only contain non-primary key attributes error. Every written NOT
    counts, two as much as one, and so do NOT IN, NOT BETWEEN, IS NOT MISSING and IS NOT <type>. A NOT wrapping such an OR is refused too, as
    is one over an AND such as NOT (sk = 's0' AND x = 0). A partition key of
    the wrong type is reported first. On an index the check uses the index's
    keys. These used to run, or fail as too complex or as overlapping key
    conditions. Captured against eu-west-2 and us-east-1 on 5 and 6 November
    2026 (#282).
  • A PartiQL SELECT runs attribute_exists, attribute_not_exists or IS MISSING on a key beside a branch naming no key attribute, such as
    pk = 'k' AND (attribute_not_exists(sk) OR x = 1), as a filter over the
    partition, on tables and on both kinds of index. It used to be refused for
    overlapping key conditions. Captured against eu-west-2 and us-east-1 on
    6 November 2026.
  • PartiQL SELECT reads one partition when every OR branch names the same
    partition key. It used to scan the table, charging for unrelated rows and
    counting them towards Limit. Separate parameters holding the same key,
    including equivalent numeric spellings, use the same partition read.
    Captured against eu-west-2 and us-east-1 on 23 October 2026
    (#229,
    #269, thanks
    @jay23606).
  • A PartiQL OR of sort-key conditions reads only their union within the
    shared partition, on tables and on global and local secondary indexes,
    including beside a filter too wide to expand. A Limit read that ends on
    the last of a set of sort keys, or on a range's closed bound, returns no
    NextToken, so two keys under Limit: 1 take two pages rather than
    three, on an index and under ORDER BY too.
    Read capacity is charged per OR branch, as DynamoDB charges it, so each
    requested key costs a read whether or not it exists. Captured against
    eu-west-2 and us-east-1 on 3 and 4 November 2026
    (#271).
  • A PartiQL sort-key IN with more than one value reads, charges and pages
    like the OR of its keys, on tables and on global and local secondary
    indexes. It used to read the whole partition, so pk = 'k' AND sk IN ['row-1', 'row-3'] cost what the partition did and a Limit walk
    kept its token past the last key. Each listed key is charged a read whether
    or not it exists, and a last listed key with no item keeps the token for one
    empty page, as the OR form does. Captured against eu-west-2 and us-east-1 on
    5 November 2026
    (#289).
  • PartiQL accepts ORDER BY on the sort key when OR branches share one
    partition. It used to count that partition more than once and demand the
    partition key in ORDER BY
    (#273).
  • A PartiQL filter on an attribute an index doesn't project is refused when
    OR branches share the index partition key, including through one
    multi-value IN. It used to return no items
    (#272).
  • PartiQL evaluates large OR filters as a tree when expanding their
    combinations would exceed the read planner's budget. A partition key
    equality beside the filter still reads that partition. Nine, sixteen and
    forty pairs of OR conditions now run, with key-type and overlapping-range
    checks preserved when the filter exceeds the expansion budget. A string
    partition key given 1 and 1.0 is refused for its type, where it used to
    read nothing
    (#225).
  • Request-member errors follow DynamoDB's wording and order for deep
    DeleteItem, PutItem and UpdateItem requests. An UpdateItem without
    a key joins an empty table name or invalid ConditionalOperator with the
    missing-key error, and Query reports a misused ConditionalOperator before
    an invalid Select. A deep PutItem, UpdateItem or DeleteItem reports
    every invalid member together, in DynamoDB's order: the enum members, a
    missing Item or Key, and a missing or empty table name. As in DynamoDB,
    a table name's length and pattern are reported only once those pass
    (#262).
  • ExecuteStatement reads Limit as any JSON number, as DynamoDB does. A
    fraction truncates, so 1.5 and 1.0 read as 1, and a value past
    2147483647, such as 1e+20, one near or past 9223372036854775807, or
    1e400, reads every row. These used to be refused with serde's own message
    or fail the read. A Limit of -1 is refused with Member must have value greater than or equal to 1, echoing the value and listed with the
    request's other member errors, and -1e400 echoes -2147483648. Captured
    against eu-west-2 and us-east-1 on 5 and 6 November 2026
    (#287).
  • Query's Limit and Scan's Limit, Segment and TotalSegments read a
    number past the range of a double, such as 1e400 or -1e400, as the
    32-bit integer it saturates to, and check it as they check any other
    value. They used to answer with a bare SerializationException. A Limit
    of 0.0 or -0.0 is reported as Value '0' at 'limit', as 0.5 is,
    where it used to get the message for a Limit of 0. Captured against
    eu-west-2 and us-east-1 on 6 November 2026.
  • A number where a string or boolean member belongs, such as TableName,
    Select or ConsistentRead, is named by how it is written, as DynamoDB
    names it. A whole number gets NUMBER_VALUE cannot be converted to String
    (or Boolean) at any size, including -0, 100000000000000000000 and a
    400-digit number, and one written with a point or an exponent gets
    DECIMAL_VALUE, including 1e400. In a string member, -0 and whole
    numbers past 64 bits used to get DECIMAL_VALUE, and anywhere, a number
    past the range of a double got a bare SerializationException. Captured against eu-west-2 and us-east-1 on
    6 November 2026.
  • A PutItem, UpdateItem, DeleteItem, GetItem, Query or Scan
    table name is measured in characters, as DynamoDB measures it, so 😀😀 is
    too short and 128 emoji aren't too long. SearchVectors shares the check.
    A deep PutItem, UpdateItem or DeleteItem measures it in UTF-16 units,
    as DynamoDB does there.
  • --port 0 reports the port the server bound. The startup line used to
    print the requested address, Dynoxide listening on http://127.0.0.1:0, so
    nothing outside the process could tell which port the OS had assigned. The
    line is unchanged for any other port
    (#277, thanks
    @samchungy).