Skip to content

Commit

Permalink
release: 2024.12rc8
Browse files Browse the repository at this point in the history
  • Loading branch information
danh91 committed Dec 17, 2024
1 parent c75a6db commit a40a880
Show file tree
Hide file tree
Showing 15 changed files with 234 additions and 234 deletions.
2 changes: 1 addition & 1 deletion apps/api/karrio/server/VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
2024.12rc7
2024.12rc8
4 changes: 2 additions & 2 deletions apps/www/openapi.yml
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ info:
## Versioning
When backwards-incompatible changes are made to the API, a new, dated version is released.
The current version is `2024.12rc7`.
The current version is `2024.12rc8`.
Read our API changelog to learn more about backwards compatibility.
Expand Down Expand Up @@ -84,7 +84,7 @@ info:
All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure).
API requests without authentication will also fail.
title: Karrio API
version: 2024.12rc7
version: 2024.12rc8
paths:
/:
get:
Expand Down
4 changes: 2 additions & 2 deletions bin/deploy-hobby
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

set -e

export KARRIO_TAG="${KARRIO_TAG:-2024.12rc7}"
export KARRIO_TAG="${KARRIO_TAG:-2024.12rc8}"
export SENTRY_DSN="${SENTRY_DSN:-'https://public@sentry.example.com/1'}"

SECRET_KEY=$(head -c 28 /dev/urandom | sha224sum -b | head -c 56)
Expand All @@ -23,7 +23,7 @@ if ! [ -z "$1" ]
then
export KARRIO_TAG=$1
else
echo "What version of Karrio would you like to install? (We default to '2024.12rc7')"
echo "What version of Karrio would you like to install? (We default to '2024.12rc8')"
echo "You can check out available versions here: https://hub.docker.com/r/karrio/server/tags"
read -r KARRIO_TAG_READ
if [ -z "$KARRIO_TAG_READ" ]
Expand Down
2 changes: 1 addition & 1 deletion bin/upgrade-hobby
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ else
fi

[[ -f ".env" ]] && export $(cat .env | xargs) || ( echo "No .env file found. Please create it with SECRET_KEY and DOMAIN set." && exit 1)
export KARRIO_TAG="${KARRIO_TAG:-2024.12rc7}"
export KARRIO_TAG="${KARRIO_TAG:-2024.12rc8}"

# get karrio scripts
mkdir -p ./karrio
Expand Down
2 changes: 1 addition & 1 deletion docker/.env
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ REDIS_PORT=6379
# API - Configuration for the Nginx Reverse proxy.
############

KARRIO_TAG=2024.12rc7
KARRIO_TAG=2024.12rc8
KARRIO_HTTP_PORT=5002

############
Expand Down
2 changes: 1 addition & 1 deletion ee/insiders
48 changes: 24 additions & 24 deletions modules/connectors/seko/tests/seko/test_tracking.py
Original file line number Diff line number Diff line change
Expand Up @@ -123,19 +123,19 @@ def test_parse_tracking_response_multiple(self):
"carrier_name": "seko",
"delivered": False,
"events": [
{
"code": "AAY",
"date": "2024-10-25",
"description": "Pre-advice received",
"time": "11:28 AM",
},
{
"code": "OP-1",
"date": "2024-10-25",
"description": "Tracking number allocated & order ready",
"location": "LONDON,EGHAM,GB",
"time": "10:28 AM",
},
{
"code": "AAY",
"date": "2024-10-25",
"description": "Pre-advice received",
"time": "11:28 AM",
},
],
"status": "in_transit",
"tracking_number": "DG30754101650",
Expand All @@ -145,19 +145,19 @@ def test_parse_tracking_response_multiple(self):
"carrier_name": "seko",
"delivered": False,
"events": [
{
"code": "AAY",
"date": "2024-10-25",
"description": "Pre-advice received",
"time": "11:56 AM",
},
{
"code": "OP-1",
"date": "2024-10-25",
"description": "Tracking number allocated & order ready",
"location": "LONDON,EGHAM,GB",
"time": "10:56 AM",
},
{
"code": "AAY",
"date": "2024-10-25",
"description": "Pre-advice received",
"time": "11:56 AM",
},
],
"status": "in_transit",
"tracking_number": "DG30754101664",
Expand All @@ -167,19 +167,19 @@ def test_parse_tracking_response_multiple(self):
"carrier_name": "seko",
"delivered": False,
"events": [
{
"code": "AAY",
"date": "2024-10-25",
"description": "Pre-advice received",
"time": "11:57 AM",
},
{
"code": "OP-1",
"date": "2024-10-25",
"description": "Tracking number allocated & order ready",
"location": "LONDON,EGHAM,GB",
"time": "10:57 AM",
},
{
"code": "AAY",
"date": "2024-10-25",
"description": "Pre-advice received",
"time": "11:57 AM",
},
],
"status": "in_transit",
"tracking_number": "DG30754101665",
Expand All @@ -189,19 +189,19 @@ def test_parse_tracking_response_multiple(self):
"carrier_name": "seko",
"delivered": False,
"events": [
{
"code": "AAY",
"date": "2024-10-25",
"description": "Pre-advice received",
"time": "12:02 PM",
},
{
"code": "OP-1",
"date": "2024-10-25",
"description": "Tracking number allocated & order ready",
"location": "LONDON,EGHAM,GB",
"time": "11:02 AM",
},
{
"code": "AAY",
"date": "2024-10-25",
"description": "Pre-advice received",
"time": "12:02 PM",
},
],
"status": "in_transit",
"tracking_number": "DG30754101666",
Expand Down
4 changes: 2 additions & 2 deletions packages/types/rest/api.ts
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@
/* eslint-disable */
/**
* Karrio API
* Karrio is a multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.12rc7`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail.
* Karrio is a multi-carrier shipping API that simplifies the integration of logistics carrier services. The Karrio API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The Karrio API differs for every account as we release new versions. These docs are customized to your version of the API. ## Versioning When backwards-incompatible changes are made to the API, a new, dated version is released. The current version is `2024.12rc8`. Read our API changelog to learn more about backwards compatibility. As a precaution, use API versioning to check a new API version before committing to an upgrade. ## Environments The Karrio API offer the possibility to create and retrieve certain objects in `test_mode`. In development, it is therefore possible to add carrier connections, get live rates, buy labels, create trackers and schedule pickups in `test_mode`. ## Pagination All top-level API resources have support for bulk fetches via \"list\" API methods. For instance, you can list addresses, list shipments, and list trackers. These list API methods share a common structure, taking at least these two parameters: limit, and offset. Karrio utilizes offset-based pagination via the offset and limit parameters. Both parameters take a number as value (see below) and return objects in reverse chronological order. The offset parameter returns objects listed after an index. The limit parameter take a limit on the number of objects to be returned from 1 to 100. ```json { \"count\": 100, \"next\": \"/v1/shipments?limit=25&offset=50\", \"previous\": \"/v1/shipments?limit=25&offset=25\", \"results\": [ { ... }, ] } ``` ## Metadata Updateable Karrio objects—including Shipment and Order have a metadata parameter. You can use this parameter to attach key-value data to these Karrio objects. Metadata is useful for storing additional, structured information on an object. As an example, you could store your user\'s full name and corresponding unique identifier from your system on a Karrio Order object. Do not store any sensitive information as metadata. ## Authentication API keys are used to authenticate requests. You can view and manage your API keys in the Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your API token as the basic auth username value. You do not need to provide a password. ```shell $ curl https://instance.api.com/v1/shipments \\ -u key_xxxxxx: # The colon prevents curl from asking for a password. ``` If you need to authenticate via bearer auth (e.g., for a cross-origin request), use `-H \"Authorization: Token key_xxxxxx\"` instead of `-u key_xxxxxx`. All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). API requests without authentication will also fail.
*
* The version of the OpenAPI document: 2024.12rc7
* The version of the OpenAPI document: 2024.12rc8
*
*
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
Expand Down
Loading

0 comments on commit a40a880

Please sign in to comment.