Support Shopify API version 2020-07
See original GitHub issueNow that 2020-07 is available, and 2019-07 is the oldest supported version, I want to start updating the package to target 2020-07.
I might be interested in exploring a different versioning scheme for the package based on the Shopify API version. Something like 2020.07.0, 2020.07.1, etc. I think we’ve talked about it elsewhere in this repo and I decided against it at the time, but I can’t find a link at the moment. I’d be interested in hearing arguments for or against changing the versioning scheme. For reference, we’re currently using the typical SemVer scheme e.g. 5.0.0
, 5.0.1
, 5.1.0
, etc.
TODO
- Implement the new Collections endpoint (smart collections no longer supported on current Collects endpoint) (#539)
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (5 by maintainers)
Top Results From Across the Web
API version 2020-07 is now stable and ready for general usage
The 2020-07 release adds Amazon EventBridge support, enabling you to receive Shopify webhooks using an event bus. Version 2020-07 also adds ...
Read more >API Deprecation at Shopify: 2021-07 Edition
The 2021-07 version will become stable and ready for general usage. The 2020-07 version will become unsupported. Requests that have been ...
Read more >Shopify API Release: July 2020
As of version 2020-07, the Billing API has support for annual charges, including prorated upgrades and automatic renewal. Use the ...
Read more >API Deprecation at Shopify: 2021-04 Edition
Below are the breaking changes introduced in 2020-07, which will become Shopify's oldest supported version on April 1st. 1. Allocation method ...
Read more >Prepare for Shopify API version changes on Jan. 1, 2021
Shopify has announced that version 2020-01 will no longer be supported on Jan. 1, 2021, when version 2021-01 is released. The planned ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @nozzlegear , it seems that we can easily create or update products with SEO title and description metafields using the new API version. Hope you will integrate this while upgrading to 2020-07 version.
https://shopify.dev/docs/admin-api/rest/reference/products/product?api[version]=2020-07
Update a product’s SEO title and description PUT /admin/api/2020-07/products/632910392.json { “product”: { “id”: 632910392, “metafields_global_title_tag”: “Brand new title”, “metafields_global_description_tag”: “Brand new description” } }
Luckily upgrading to more recent versions will be MUCH MUCH easier that the previous time. I had a quick look at the release notes and these are the changes I have found (related to the admin REST API only).
2020-01 Breaking change: Smart collections cannot use the Collect endpoint anymore => Must implement new Collections endpoint. https://shopify.dev/docs/admin-api/rest/reference/products/collection
New Fulfillment orders endpoint: would be nice but not necessarily required since it is a new service so there would be no breaking change
2020-04 New fields on Location, Order, Refund, AbandonedCheckout, Fulfillment
2020-07 ProductVariant.images is removed
That’s not much. The biggest piece will be implementing the new Collection endpoint in 2020-01. As a result, I think it’s perfectly reasonable to upgrade ShopifySharp straight to the latest 2020-07 version.
Regarding ShopifySharp’s versioning, I have gone back and forth but my latest personal preference would be to keep doing things as we have done so far. That is, normal semver without incorporating the underlying Shopify API version (e.g. 202001) into it. Incorporating the API version into the lib version will likely break the semver semantics (used by NuGet) and / or make it awkward.
I think that documenting the API version used in the
readme.md
is enough.