Skip to content

v1.2.0

Choose a tag to compare

@github-actions github-actions released this 27 Aug 20:40
· 5 commits to main since this release

Added

  • Bearer-token users with mods_manage or solder_full permission can read /api/mod endpoints when public mod API access is disabled with SOLDER_DISABLE_MOD_API=true
  • GET /api/mod/{slug}/{version} responses now include accessible build memberships and their owning modpack metadata
  • Build mod list filtering by mod name, slug, and selected version

Changed

  • Development Compose stack now uses the isolated technicsolder-dev project instead of sharing production containers and volumes
  • Password fields now identify current and new credentials correctly to password managers
  • Distributed environment example now enables persistent Redis connections to prevent ephemeral-port exhaustion under sustained high concurrency
  • npm dependency lifecycle scripts are disabled and dependency updates are delayed for seven days to reduce supply-chain exposure; Renovate security updates remain exempt from the delay
  • Updated PHP, frontend, build, and CI dependencies, including Laravel 13.26, Guzzle 7.15, Alpine.js 3.16, Tailwind CSS 4.3, Vite 8.2, Node.js 24.18, actions/checkout 7, and actions/setup-python 7

Fixed

  • PostCSS and nanoid updated to fix source map path traversal and unbounded generator loop vulnerabilities
  • Delegated user managers can no longer grant permissions they do not hold or manage users with greater permissions or broader modpack access
  • The final solder_full user can no longer demote themselves, regardless of their database ID
  • Profile-only and password-only user updates no longer revoke permissions omitted from the request
  • Password changes now require the acting user's current password, including when a manager resets another user's password; malformed password values return a validation error
  • Login throttling now canonicalizes email casing and Unicode variants, preventing equivalent addresses from receiving separate rate-limit buckets
  • Login details, update checks, and password rehashing now occur only after authentication and two-factor challenges complete successfully
  • Users can no longer delete their own accounts