What ruby-grape/grape shipped

This week in Grape: Grape.config.allow_undeclared_params, an RFC 9457 problem details formatter, fixes for optional segments under namespaces and helper visibility, eager loading of mounted Rails APIs at boot, and new minimums of Rack 3.1 and ActiveSupport 8.0.

This week in Grape: Grape.config.allow_undeclared_params lets an endpoint answer 400 to params it did not declare, defaulting to true with false as the 5.0 default. A new error formatter answers as RFC 9457 problem details. Fixes land for a route opening with an optional segment under a namespace, for helpers reached from routes declared above them in the same scope, and for cascading past a mounted Rack app declining with lowercase x-cascade. Rails apps with eager_load on now compile mounted APIs when routes load, and API.eager_load! compiles an API and loads its translations. Grape now requires Rack 3.1 and ActiveSupport 8.0.

Grape 4.1.0 is out. Fixes cascade routing to return 404 when all routes decline, resolves file upload issues in oneof validators, and clears all RuboCop violations.

Grape 4.1.0 is now available. This release includes a fix for cascade routing to properly return 404 responses when all routes on a path decline requests, resolves file upload issues in oneof validators, refactors router methods for clearer logic, and completes RuboCop violations cleanup across the codebase.

This week: Rack::Head now wraps the whole router so HEAD responses from mounted apps lose their bodies. New setting to let rescue_from exceptions propagate to middleware. Added:md and:jsonl formats. */* negotiation keeps your content type order.

This week in Grape: Rack::Head now wraps the router rather than each endpoint's stack, so HEAD requests through mounted Rack apps also have their bodies stripped. A new setting lets an exception raised in a rescue_from block propagate to Rack middleware above Grape. Two formats were added::md/:markdown, which renders an object's to_markdown, and:jsonl for JSON Lines. Content type negotiation for */* now keeps each API's declared order. InheritableSetting's scalar settings and scope flags are now defined by key.

This week: a logger set on one API no longer overrides every other API's logger. Requests also allocate less when presenting entities and reading path params. Internally, the raised RuboCop overrides for module length, ABC size and complexity are gone, with behaviour unchanged.

This week's changes in grape: A logger set on one API no longer replaces the logger for every other API. Previously the logger lived in a hash shared by the whole process, so the last API to set one decided where all APIs logged. Requests allocate less when presenting an entity or reading path params. Four per-request allocations that only existed to feed another one were removed, and each request's endpoint is copied from a prototype without route-building state. requires and optional now share one definition instead of duplicating their signature and deprecated positional-options check. Internally, the raised RuboCop overrides for module length, ABC size, cyclomatic complexity and perceived complexity are removed, with methods split to meet the defaults. Behaviour is unchanged.

Grape 2.2 fixes error handling in transactions, validates params correctly in nested scopes, rejects malformed numbers, and eliminates unnecessary per-request middleware copying.

This week's Grape releases address critical correctness issues: error! now properly raises exceptions for database transaction safety, required params reject nil in nested scopes, Integer params reject fractional numbers, and header versioning handles hyphens. We also eliminated per-request middleware copying to reduce overhead on the happy path.

Grape 4.0 improvements shipping this week: mounted Rack apps now route correctly, request overhead cut by removing middleware copying, and validation handles invalid UTF-8 bytes gracefully.

This week in Grape: mounted Rack apps now route as ANY methods in declaration order, request performance improved by eliminating formatter copying and empty filter phases, Rails initialization fixed in CI, header versioning matches capital letters correctly, custom coerce messages are honored, and nested array validation errors now report accurate indices. Several edge cases in validation and routing are now handled properly.

Grape v4.0.1 ships with significant performance improvements: fewer allocations per request, smarter registry handling, and optimized path matching. Plus comprehensive README corrections ensuring examples match actual behavior.

Grape v4.0.1 is out with meaningful performance work: shared Rack lambda per endpoint, optimized registry writes, removed unused match caches, and faster path-versioned requests. We also corrected roughly 40 README passages to match actual behavior, improving the experience for developers discovering and using the framework.