Karrio OSS 2024.6 #668
danh91
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Important
Thank you for your patience as I go through a time of workload adjustment between my new role and the maintenance of Karrio. Read my community announcement here
Feat
karrio.libto document template contextfedex_wsDisable "note" alert types as previously done in fedex_ws #638usps_wt(for USPS Web Tools)signed_by#635upsextensionhay_postintegrationeShippernew API integrationreturn_addressfieldeshipperAPI extensioncarrier_idto thePOST /v1/proxy/shipping/{carrier_name}/cancelto allow precise carrier account selection for the operation. #590Fix
eshippercancel shipment request, and add special cancel error handling for undocumented errorseshipperdatetimerequirement for ship date and update tests for order cancellationfedextracking estimated delivery date response parsingeshipperforcarrier_nameuspsAPI token missing scopeeshipperdimension parsing requirements2024.6-rc24): migration race condition issue #645providers.MODELSdynamic object created by old carrier settings models2024.6-rc24: regression on carrier configurationtest_modeassignment for carrier connection registration in live mode.eshipperdatabase migration leaving orphan carrier datacarrier_idcheck"variableOptions"format issueDocs
docusaurusdocusaurus-openapi-docspluginChore
eshippercredential transfer from username|password to principal|credentialsedcommand/admin/user_accounts trying to add a new user account does not get addedBreaking changes
AM/PM)eshipper_xmlextensioneshiper->eshipper_xmlto prepare for the upgrade to the new eShipper APIPOST /v1/documentstoPOST /v1/documents/uploadsGET /v1/documentsendpoint returning ETD upload records is nowGET /v1/documents/uploadsCaution
Please make sure to update your deployment environment variables for the dashboard when upgrading to
rc10 +Check out the docs here and the following files to make sure you have the right environment variables especially if you are not using our public docker-compose files and have a custom deployment or hosted on something live Vercel.
Special thanks to contributors: @ChrisNolan (🎉 first contribution), @jacobshilitz and @david-kocharyan
🚀 Celebrating a new sponsor:
@ alissonf216
This discussion was created from the release Karrio OSS 2024.6.
Beta Was this translation helpful? Give feedback.
All reactions