[patch] 2026.1.5 #953
Open
[patch] 2026.1.5 #953
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nt KeyError when key is missing
Design document for deprecating POST /v1/pickups/{carrier_name}/schedule
in favor of POST /v1/pickups with carrier_code and options.connection_id
in the request body, matching the shipments API pattern.
Add POST handler to PickupList view so GET /v1/pickups lists pickups and
POST /v1/pickups creates them, matching the shipments API pattern.
Backend changes:
- Add carrier_code field to PickupRequest serializer
- Resolve carrier from body fields (carrier_code, options.connection_id)
when no URL-based carrier_filter is provided
- Exclude carrier_code from gateway payload to avoid SDK errors
- Mark legacy POST /v1/pickups/{carrier_name}/schedule as deprecated
with Deprecation and Link headers
Tests:
- Add TestPickupScheduleNewAPI: carrier_code, connection_id, standalone,
validation
- Add TestLegacyEndpointDeprecation: deprecation headers, backward compat
- Update response fixtures to include carrier_code field
… API - Change schedulePickup mutation from generated REST client with carrierName URL param to direct axios POST /v1/pickups - Add connection_id to form state and use it as carrier dropdown value to support multiple connections per carrier - Send carrier_code and options.connection_id in request payload
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
danh91
force-pushed
the
patch-2026.1.5
branch
from
4828846 to
e0f781c
Compare
Add pickup status field (scheduled/picked_up/cancelled/closed) to the pickup model with a database migration. Implement pickup lifecycle event signals (pickup_scheduled, pickup_cancelled, pickup_closed) and background tasks. Update GraphQL schema to expose status field on pickup queries. Add status column and conditional cancel action to pickups table.
…ng support Add status filter for pickup list queries. Update gateway to support carrier-agnostic pickup scheduling via carrier_code. Extend core serializers with pickup status field support and filter abstractions.
Regenerate OpenAPI schema, GraphQL introspection schemas, and REST client types reflecting pickup status field, carrier-agnostic scheduling endpoint, pickup lifecycle events, and updated pickup API documentation.
Update schedule pickup dialog for carrier-agnostic API. Adjust pickup hooks to work with the new POST /v1/pickups endpoint.
Add pickup preview sheet (side panel) matching the shipment detail sheet pattern. Includes pickup detail view with header, status badge, details sidebar (carrier, confirmation, dates, time window, location), pickup address, parcels, related shipments table with tracker status, tracking records from related shipments, metadata viewer, and activity timeline with API logs and system events. Expand GET_PICKUP GraphQL query to include tracker data on related shipments. Add View details menu option and clickable table rows on the pickups list page.
Add tests for carrier-agnostic pickup scheduling, status transitions, and pickup lifecycle event handling.
Rename CARRIER_CONNECTION_ARCHITECTURE.md to use hyphenated casing (CARRIER-CONNECTION-ARCHITECTURE.md) for consistency.
…se-parsing fix(fedex):TypeError in pickup cancel response parsing when output is None
fixes: PostAt/Austrian post
fixes: ParecelOne
Add a dedicated tracker detail page at /trackers/[id] with tracking events timeline, shipment link, metadata editor, and ActivityTimeline for API logs, traces, and system events. Augment the tracker preview sheet with a condensed activity section and "View all" navigation. - Create TrackerComponent with entity-based log/event filtering - Add stacked layout mode to ActivityTimeline for inline detail viewing - Add condensed prop to ActivityTimeline for compact rendering - Fix infinite re-render in trackers list (searchParams object ref) - Fix infinite re-render in trackers filter (variables object ref) - Fix preview sheet showing unrelated logs (hooks initialized before tracker selection)
…ents Stabilize useEffect dependencies across all list pages and filter components to prevent maximum update depth errors. Replace object reference dependencies with stable string representations. - Use searchParams.toString() instead of searchParams object in Shipments, Pickups, Orders, Manifests, and Workflows list pages - Use JSON.stringify(variables) instead of variables object in shipments-filter and orders-filter components
Replace jinja2.Template() with jinja2.sandbox.SandboxedEnvironment in the document generator and workflow automation engine to prevent Server-Side Template Injection allowing authenticated users to execute arbitrary Python code via crafted document templates. Reported by: i0.rs (Georgios Tsimpidas, Edward Passenidis)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Karrio 2026.1.5
Changes
Feat
Test
Chore
Docs