github ulsklyc/yuvomi v2.92.0

one hour ago

Changed

  • Notes, birthdays and quick links check every request against the published API description.
    This is about your own API clients; the app sends nothing that changes. Under
    /api/v1/notes, /api/v1/birthdays and /api/v1/quick-links, input that used to be
    quietly accepted or reinterpreted is now refused with a 400:

    • a path id that is not plain digits, such as 12abc (it was read as 12);
    • pinned as "false", 5 or "x", and pinned: null on a note update;
    • a number in a text field, such as "title": 5 (it was stored as text);
    • an id written as text in category_ids and contact_id, and anything but whole numbers
      in contact_ids (birthday import) and ids (quick link order). Note category reordering
      still takes digit strings, because the app sends them;
    • a list instead of an object as the body;
    • a quick link visibility other than all, private or null (it became all or was
      ignored);
    • an empty name when updating a birthday or a quick link.

    Such a refusal reads { "error": "The request does not match the documented schema.", "code": 400, "reason": "validation", "fields": [{ "path": "body/title", "rule": "type" }] }.
    fields names the place and the JSON Schema rule, never the value you sent. Input that was
    already refused before can now get this form instead of the old sentence. The check runs
    before the entry is looked up, so a bad request for a missing or locked entry is now a 400,
    not a 404 or 403, and a missing body where one is required is a 400. Text lengths count the
    value as sent, before surrounding spaces are trimmed. Unknown fields are still ignored, and
    what stays allowed is in the description too: null or "" for "no value", the note
    visibilities family and shared, year_unknown: null, a pin toggle without a body, and
    reminder fields as text or number.

  • Birthdays answer an unexpected failure with the same sentence as the rest of the API. The
    seven routes under /api/v1/birthdays (list, upcoming, create, import candidates, import,
    update, delete) said "Internal error." on a server-side failure; they now say
    "Internal server error." like every other module. Status 500 and code are unchanged.

  • Reminders, notification channels, modules, permissions, e-mail and weather check every
    request against the published API description.
    This is about your own API clients; the app
    sends nothing that is refused now (a task reminder now goes out with its id as a number).
    Under these six prefixes, input that used to be quietly accepted or reinterpreted is now
    refused with a 400:

    • everywhere: a path id that is not plain digits, such as 12abc, 5.0, 1e2 or 0x10
      (it was read as another number or looked up as 12), and a query value given twice where
      one is expected (audience, admin, city, lang, entity_id);
    • /api/v1/reminders: entity_id as 1abc or 1.9 (it was read as 1), an unknown
      entity_type, remind_at as a list, and a time the route never read - a lowercase t
      or z, a space instead of T, an offset of hours only (+02). A body that is not an
      object or a remind_ats that is not a list is refused before the entry is looked up;
    • /api/v1/notifications: a provider that is not exactly gotify, ntfy, webhook or
      email (" NTFY " was accepted), a number as name, enabled as "false" (it switched
      the channel ON), config or secrets as null, and clearSecrets that is not a list of
      names (a number was a 500). A provider sent with an update must be a known one, too;
    • /api/v1/modules: overwrite as true or yes on a ZIP install (true replaced, yes
      was ignored), overwrite: "1" on a GitHub install, a path over 500 characters as sent,
      ref or path that is not text, and an asset address without a file path (it was a 404);
    • /api/v1/permissions: no body, a list as the body and capabilities: null (all three
      answered 200 and REMOVED the stored rights), a map that is not an object, an access level
      other than none, read, write (modules) or none, allow (widgets, capabilities),
      and a member id such as 12abc or 1.5;
    • /api/v1/email: a missing body on PUT /config (it was a 200 that saved nothing), port
      as text, a truth value, a list or "" ("587" was stored as text), a number or truth
      value as host, user, fromName, fromAddress or pass, clearPassword: "true", a
      secure that is not one of its three values, and to: null or a number on POST /test;
    • /api/v1/weather: a place name given twice, and an icon code other than 2 to 4 letters or
      digits.

    What stays allowed is in the description now too: entity_id as digit text on
    POST /reminders, every time form the reminder routes read (a date alone, no seconds, a
    fraction, Z, +02:00 or +0200), up to five reminders counted after conversion, a
    partial channel update, null to clear an e-mail field, any lang on the weather routes
    (de-AT, an unknown code falls back), admin and audience as any text. A refusal's
    reason can now be the route's own documented reason instead of validation, and an entry
    in fields can carry it as reason: bad_url (GitHub URL missing, not text or too long),
    email_port_invalid, email_from_invalid (a sender that is neither text nor null) and
    name_too_short (a place name that is missing, empty or given twice) keep the reason they
    had. The check runs after the admin, session and rate-limit checks, so a member still gets
    403, and before the entry is looked up, so a bad request for a missing channel, member or
    reminder target is now a 400, not a 404.

  • Family, profile pictures, search, kitchen, screensaver and wall displays check every request
    against the published API description.
    This is about your own API clients; the app sends
    nothing that is refused now. Under these prefixes, input that used to be quietly accepted,
    reinterpreted or answered later is now refused with a 400:

    • everywhere: a path id that is not plain digits, such as 12abc, 5.0, 1e2 or 0x10
      (5.0 and 1e2 were read as 5 and 100), and a query value given twice where one is
      expected (q on /api/v1/search searched for a,b, today on /api/v1/kitchen/summary);
    • /api/v1/family/members/reorder: the order is checked before the members are looked up.
      It keeps its reasons invalid_order and duplicate_member, now with fields. A member who
      is not an administrator gets 403 for any body, as before;
    • /api/v1/people/{id}/avatar: a missing v, one that is not 32 lowercase hex characters,
      or one given twice (it was a 404). A well-formed key that does not match is still a 404;
    • /api/v1/kitchen/summary: today that is neither YYYY-MM-DD nor empty (it fell back
      to the household day). An empty or missing today still means the household day;
    • /api/v1/screensaver: no body or a list on PUT /config (it was a 200 that saved
      nothing), url or albumId that is not text (they were read through String(), so a
      list with one URL was stored), a url over 2048 or an apiKey over 1000 characters as
      sent, an apiKey that is not text (it was ignored), clearApiKey: "true", and a photo id
      that is not a UUID - also when Immich is not set up (that was a 404). url, albumId and
      the key length keep immich_url_invalid, immich_album_id_invalid and
      immich_api_key_invalid, and a refused body stores no field at all;
    • /api/v1/displays: a display_name that is a number, a truth value, a list (they were
      stored as text) or empty, or longer than 128 characters as sent; show_screensaver as
      text; on POST /displays/pair a missing code, a code or label that is not text and a
      label over 120 characters (it was cut). A refused pairing counts against the rate limit
      like any attempt and leaves a signed-in session in place.

    What stays allowed is in the description now too: q of any length, an empty today, a
    day of the right shape that does not exist (compared as text, as before), "" to clear the
    Immich URL and album, a photo id in either letter case, label: null or "". Rules the
    description cannot carry stay with the routes and their sentences: a member order that is
    incomplete or names someone outside the household, the Immich URL scheme and album UUID
    after trimming, a display name of spaces only, equal night hours. The check runs after the
    admin check and the pairing rate limit, so a member still gets 403.

  • Recipes, recipe providers and the pantry check every request against the published API
    description.
    This is about your own API clients; the app sends nothing that is refused now
    (it sends storage location ids as numbers from this release on). Under /api/v1/recipes,
    /api/v1/recipe-providers and /api/v1/pantry, input that used to be quietly accepted,
    reinterpreted or answered later is now refused with a 400:

    • everywhere: a path id that is not plain digits, such as 12abc, 5.0, 1e2 or 0x10
      (DELETE /recipes/42abc deleted recipe 42, and 0x1e or 31.0 deleted provider account
      30 or 31), a query value given twice, a number, truth value, list or object in a text
      field (it was stored as text), and a number written as text ("5", true and [5] were
      read as numbers);
    • /api/v1/recipes: ingredients that is null, not a list, or holds entries that are not
      objects (null emptied the list, odd entries were skipped), servings outside 1 to 99 or as
      text or "", meal_types that is neither a list of texts, a text nor null, listId and
      ingredientIds of the transfer to a shopping list as text, and pantryItemId: "" on an
      ingredient match (it cleared the match; null or leaving it out still does);
    • /api/v1/recipe-providers (admin only): a provider other than mealie or tandoor
      (an unknown one was stored as mealie; left out it still is), enabled that is not a
      real truth value ("false" switched an account ON, null and 0 OFF), and a PATCH
      without a body. A base or external address that does not start with http:// or
      https:// keeps its reason recipe_providers_url_invalid or
      recipe_providers_external_url_invalid, now with fields;
    • /api/v1/pantry: a unit outside the unit list (it became pcs, and on PATCH it
      overwrote the stored unit), a quantity or minimum as text or below zero, min_quantity: ""
      (use null to clear), expires_on that is not YYYY-MM-DD, empty or null, a storage
      location id that is neither a whole number nor digit text, a PATCH without a body,
      items or changes that is not a list (null or text took over or undid nothing), an
      order of storage locations with entries that are not ids ([{}] and [true] were a
      500, other entries were skipped), and undo entries that are not the shape the take-over
      answered with.

    What stays allowed is in the description now too: null or "" for "no value" where the
    routes read it so, meal_types as comma text, unknown recipe meal types (dropped), an
    address in upper case or with leading spaces, "" for no external address, digit text for a
    storage location id (older app versions send it), null to keep a pantry item's unit or
    category on a change, {} on a partial update and on the provider test and sync. A PUT
    replaces the whole recipe or pantry item, as before: left-out fields are cleared, and only
    the name is required. Rules the description cannot carry stay with the routes and their
    sentences: an empty name after trimming, a day that does not exist, a category or storage
    location that does not exist, the image content, a provider address in a private network.
    The admin check of the providers and the second module right of the recipe transfer, the
    ingredient match and the shopping-list take-over run first, so a caller without them still
    gets 403 for any body; the check then runs before the entry is looked up, so a bad request
    for a missing entry is a 400, not a 404 or 409. Text lengths count the value as sent.

  • Reminders, notification channels, modules and e-mail answer an unexpected failure with the
    same sentence as the rest of the API.
    Their routes said "Internal error." (reminders,
    notification channels including a failed channel test, e-mail) or "Module install failed.",
    "Module delete failed.", "Module install info failed.", "Module list failed.",
    "Module update failed." and "Module asset failed." (modules) on a server-side failure;
    they now say "Internal server error." like every other module. Status 500 and code are
    unchanged, a failed channel test still stores its error on the channel, and every answer
    that names a known cause (a refused input, busy, not_writable, an install refusal with
    its reason) stays as it was. Permissions and weather answered this way already.

  • Recipes answer an unexpected failure with the same sentence as the rest of the API. The
    recipe routes (list, create, update, delete, own image, transfer to the shopping list,
    ingredient match) said "Internal error" on a server-side failure; they now say
    "Internal server error." like every other module. Status 500 and code are unchanged. The
    image proxy of imported recipes keeps its own answers (404, 502). Recipe providers and the
    pantry answered this way already.

Fixed

  • The calendar search no longer loses upcoming events behind old ones. With more than 100
    matching events it kept the oldest, so an old series or a year of past events pushed the
    upcoming ones out of the result. It now keeps upcoming events and series first, then past
    events from the newest - like the global search. The order of the result is unchanged.
  • Search and the overview show rows that tie in the same order on every load. Lists that
    sort by date or title had no unique last sort key, so entries with the same date or the same
    title could swap places between two loads, and the global search could drop exactly the newest
    of several past events with the same start when it cut its candidates. Ties now follow the
    direction of the list: newest first breaks them with the newer entry, all others with the
    older; two recipes with the same title stand in the order they were created.
  • Confirming which pantry row a recipe ingredient means names the ingredient in English.
    PUT /api/v1/recipes/{id}/ingredient-match with an empty, blank or too long name answered
    "Zutat is required.", "Zutat must not be empty." or "Zutat may be at most 200 characters long." - a German word in an English message. It now says "Ingredient ...". Status and
    code are unchanged.
  • Taking checked shopping items into the pantry no longer fails with a server error when a
    storage location was deleted meanwhile.
    If one of the chosen locations no longer exists -
    for example removed in another session while the dialog was open - the take-over now answers
    400 Location not found. like adding a pantry item does, and nothing is taken over. Before,
    the whole take-over ended as a 500.
  • The API description marks every value that may be null in the OpenAPI 3.1 way. 36 places - the
    fasting and nutrition bodies, the household setup, the waste calendar feed - said so with the
    OpenAPI 3.0 keyword nullable, which a 3.1 client generator ignores, so a generated client treated
    them as never null. They now carry null in their type. Four sample values moved from example to
    examples, and two "one of these fields" rules are spelled so that a strict JSON Schema validator
    accepts them. The API itself did not change.

Don't miss a new yuvomi release

NewReleases is sending notifications on new releases.