StackWatch

Releases

Showing the most widely used products. Choose your stack to see only what you run.

Next.jsv16.3.09d agosecuritybreakinglts
  • Fixed a security vulnerability (CVE-2025-13465) in vendored lodash
  • Stabilized several experimental features including instant navigation, app shells, and cache components
  • Enabled Turbopack build filesystem cache and TypeScript CLI by default
  • Improved performance and fixed numerous bugs across rendering, caching, and HMR systems
what breaks

Several experimental features have been stabilized and enabled by default (instant navigation, app shells, cache components, Turbopack filesystem cache, TypeScript CLI), which may change behavior for applications relying on previous defaults or experimental flags. The edge runtime has been deprecated. Some configuration options like experimental.useCache are now deprecated.

to upgrade

Review and test applications using experimental features that are now stabilized. Check if any code relies on the edge runtime (now deprecated) or experimental.useCache (now deprecated). Verify that default behavior changes for instant navigation, app shells, and cache components work as expected in your application.

advisories
changelog ↗
Ruby on Rails8.1.3.114d agosecuritybreaking
  • Active Storage now blocks libvips's unfuzzed image loaders and savers by default for security
  • Image variant transformation for BMP, ICO, and PSD files will raise errors
  • Image analysis no longer records dimensions for SVG, JPEG XL, JPEG 2000, Netpbm, and other untrusted formats
  • Minimum libvips version is now 8.13 and ruby-vips is now 2.2.1
what breaks

Applications processing BMP, ICO, PSD, SVG, JPEG XL, JPEG 2000, Netpbm, FITS, JXL, or ImageMagick-delegated formats with libvips will experience failures during image transformation and analysis. This affects any app using Active Storage with image variants on these content types.

to upgrade

If your application processes affected image types, remove them from config.active_storage.variable_content_types in an initializer to treat them as non-variable. Alternatively, upgrade libvips to 8.13+ and ruby-vips to 2.2.1+. Applications using :mini_magick can remove ruby-vips from their Gemfile to avoid the process-wide restrictions.

advisories
changelog ↗
Consulv2.0.35d agosecurity
  • Multiple security vulnerabilities fixed including DoS attacks via unbounded caching, nil-pointer panics, path normalization bypass, and unauthenticated JSON decoder attacks
  • New gRPC connection limiter configuration option (limits.grpc_max_conns_per_client) to prevent connection exhaustion attacks
  • API Gateway now correctly handles service-router configurations that compose routes across different services, namespaces, or partitions
  • New XDS configuration options for controlling server response headers on API Gateway HTTP listeners
advisories
changelog ↗
OpenSearch3.8.07d agosecurity
  • Add new API to modify data stream backing indices and multivalue_doc_count aggregation for counting documents with multiple values
  • Add HTTP/3 client support, gRPC support for Point-in-Time operations, and cross-cluster streaming via Arrow Flight
  • Improve query performance with coordinator-side field domain pruning and add security enhancements including Java deserialization filtering
  • Fix multiple bugs including snapshot listing failures, S3 encryption issues, and stack overflow vulnerabilities in deserialization
changelog ↗
Vaultv2.0.48d agosecurity
  • The changelog provided contains no substantive information about changes in this release—it only references an automated build process for artifacts.
advisories
changelog ↗
Supabasev1.26.085d agobreaking
  • Supabase Pipelines streams Postgres changes to BigQuery in near real time, now available in public alpha on all paid plans
  • Unified Logs provides a searchable view across all Supabase services with live tail and filtering in open beta
  • Edge Functions overview page now displays error rates, execution time, and CPU/memory usage metrics
  • Supabase blocks all changes to the realtime schema to prevent accidental modifications
what breaks

Extension version pinning is deprecated: from August 5, explicit versions in CREATE or ALTER EXTENSION are ignored and the default version installs with a warning. The Management API analytics/endpoints/logs.all endpoint is migrating to the new logs endpoint, requiring clients that query project logs to update. Supabase now blocks all changes to the realtime schema (creating, altering, or dropping objects fails with a permission error).

to upgrade

Update any clients that query project logs to use the new logs endpoint instead of analytics/endpoints/logs.all. Review any code that attempts to modify the realtime schema, as these operations will now fail with a permission error.

changelog ↗
Prometheusv3.13.213d agosecurity
  • Security vulnerabilities patched in golang.org/x/text and google.golang.org/grpc dependencies
  • Fixed SIGBUS crashes when the data disk is full during PromQL query execution
advisories
changelog ↗
Envoy1.39.029d agosecuritybreaking
  • Multiple security vulnerabilities fixed including HTTP/2 cookie handling, HTTP/3 QPACK denial of service, and various authorization/authentication issues
  • TLS now always enforces certificate keyUsage extension; client TLS versions are validated between 1.0-1.3
  • New HTTP filters for weighted bandwidth sharing and dynamic module capabilities expanded with new extension points
  • DNS cluster implementation unified and enabled by default; performance improvements for Prometheus scraping and large-scale stat operations
what breaks

TLS: enforce_rsa_key_usage is deprecated and ignored; Envoy now always enforces certificate keyUsage extension. TLS inspector: client TLS versions are validated and must be between TLS 1.0 and TLS 1.3. Intel DLB connection balancer (envoy.network.connection_balance.dlb) is disabled. HeaderMatcher behavior changed to evaluate header values individually instead of comma-joined. OpenTelemetry tracing may export fewer spans due to honoring request-entry sampling decisions. Build now requires Bazel 8 with WORKSPACE mode.

to upgrade

For OAuth2 security migration: enable oauth2_use_gcm_encryption, monitor oauth_legacy_cbc_decrypt counter, then disable oauth2_legacy_cbc_decrypt_compat. TLS inspector validation is revertible via envoy.reloadable_features.tls_inspector_enforce_client_tls_version. HeaderMatcher behavior is revertible via envoy.reloadable_features.match_headers_individually.

changelog ↗
Prismav0.17.08d agobreaking
  • Prisma now publishes as 17 packages under @prisma scope; applications depend on one database facade (@prisma/orm-postgres, @prisma/orm-sqlite, or @prisma/orm-mongo) instead of multiple @prisma-next/* packages
  • All errors now use a structured envelope with dotted codes (e.g., PSL.PARSE_FAILED) instead of legacy error classes and multiple error systems
  • Relation loading is now lossless: 64-bit integers arrive as bigint instead of rounding, decimals as exact strings, and temporal values decode correctly
  • PostgreSQL native types are now authored directly in type position (e.g., VarChar(255), Uuid) instead of using @db.* attributes
what breaks

Multiple breaking changes affect all users: package imports must change from @prisma-next/* to @prisma/orm-* facades; error handling code must switch from instanceof checks to isStructuredError() with dotted codes; migration manifests and contracts change format (content hashes lose sha256: prefix, snapshots move to content-addressed store); PostgreSQL schema syntax changes from @db.* attributes to native type position; relation-loading result types change (count() becomes bigint, decimals become strings); count mutation methods rename (createCount → createAndCount, etc.); and extensionPacks config key renames to extensions.

to upgrade

Follow the 0.16-to-0.17 upgrade recipe to convert migration trees and re-verify migrationHash values. Run the provided codemod to update checked-in migration trees. Regenerate your contract after upgrading. Update all error handling code to use isStructuredError() type predicate instead of instanceof. Update package.json to depend on a single @prisma/orm-* facade. Update prisma-next.config.ts to use extensions instead of extensionPacks. Rename count mutation calls (createCount → createAndCount, updateCount → updateAndCount, deleteCount → deleteAndCount). Update PostgreSQL schema to use native types directly instead of @db.* attributes.

changelog ↗
Valkey9.1.122d agosecurity
  • Security fixes for use-after-free vulnerabilities in TLS connection handling and stream RDB parsing that could enable remote code execution
  • Multiple bug fixes for crashes and undefined behavior in hash field expiration, cluster operations, and 32-bit systems
  • Improved throughput with IO threads enabled by offloading object deallocation from the main thread
  • Various ACL enforcement improvements and permission bypass fixes
changelog ↗
LangChain1.3.151d ago

No changelog text published for this release.

What's happening

12 stories

Two sources discuss the concept of avoiding being a 'meat proxy,' though the specific context and details are not provided in the excerpts given.

Elevators

12d ago

Multiple sources are reporting on elevators, though the provided excerpts do not contain sufficient detail to summarize the specific content or context of the stories.

Two discussions have emerged about intentionally creating a poor implementation of htmx, the HTML-over-the-wire library. The posts appear to be exploring what happens when htmx principles are applied badly or taken to extremes.