Releases: reactioncommerce/reaction-development-platform
v2.2.1
v2.2.1
This is a patch version change keep versioning coordinated between Reaction Platform, Reaction, Reaction Hydra, and Example Storefront.
v2.2.0
v2.2.0
This is a minor versioning release coordinated with Reaction, our Example Storefront and reaction-hydra.
v2.1.0
v2.1.0
This is a minor versioning release coordinated with Reaction, our Example Storefront and reaction-hydra.
v2.0.0
v2.0.0
This is our first release of Reaction Platform.
Reaction is API-first, real-time commerce engine built using Node.js, React, and GraphQL. It’s the second major release of our open source commerce software.
This release is coordinated with Reaction, our Example Storefront (previously Storefront Starter Kit) and reaction-hydra.
Reaction v2.0.0 is built as a truly headless commerce platform that decouples the Reaction backend services from the frontend. We’ve decoupled the storefront application from the API. Reaction platform now consists of the reaction project, which is now primarily our GraphQL API, along with our Example Storefront, which integrates with the Reaction application via GraphQL API to provide a customer-facing storefront.
New documentation
See this page for a non-comprehensive list of new and updated docs.
Some highlights:
- A Storefront UI Development guide answering "How do I build a storefront for Reaction or adapt my storefront to get its data from Reaction, without starting from an example app"
- Helpful info about GraphQL Resolvers and extending GraphQL to add a field
- A guide for “How To Extend the Product Schema”
OS notes
Support for Windows.
[reaction-platform](https://github.com/reactioncommerce/reaction-platform) is not compatible with Windows and has not been fully tested on Windows at this time.
MacOS and Linux are supported.
Reaction will support development in a dockerized environment and will focus on tooling and documentation for installation and configuration on the macOS and Linux OSes.
We've adopted the DCO
We've adopted the Developer Certificate of Origin (DCO) in lieu of a Contributor License Agreement for all contributions to Reaction Commerce open source projects. We request that contributors agree to the terms of the DCO and indicate that agreement by signing all commits made to Reaction Commerce projects by adding a line with your name and email address to every Git commit message contributed:
Signed-off-by: Jane Doe <[email protected]>
You can sign your commit automatically with Git by using git commit -s if you have your user.name and user.email set as part of your Git configuration.
We ask that you use your real name (please no anonymous contributions or pseudonyms). By signing your commit you are certifying that you have the right have the right to submit it under the open source license used by that particular Reaction Commerce project. You must use your real name (no pseudonyms or anonymous contributions are allowed.)
We use the Probot DCO GitHub app to check for DCO signoffs of every commit. If you forget to sign your commits, the DCO bot will remind you and give you detailed instructions for how to amend your commits to add a signature.
We're following in the footsteps of several other open source projects in adopting the DCO such as Chef, Docker, and GitLab
Share your feedback
We want to hear from you! Here are some good ways to get in touch.
- Want to request a new feature for Reaction? There’s now a Reaction repo just for new feature requests.
- Reaction engineers and community engineers and developers are always collaborating in our Gitter chat channel
- Ask Us Anything! Watch this space for details about an upcoming Community Q&A session with the Reaction team.
v2.0.0-rc.12
v2.0.0-rc.12
This is our fourth official release candidate for this project.
Testing Notes
The config.mk file to use the release tags coordinated across the reaction platform.
The QA for the release of this version of reaction-platform should involve testing that the projects are compatible and work together.
Running this release-candidate branch of reaction-platform should also set up the associated release branch for each of the projects in the platform. These are the versions that should be tested - that they are performing as expected, and that they are compatible with each other.
v2.0.0-rc.11
v2.0.0-rc.11
This is our third official release candidate for this project.
Testing Notes
The config.mk file to use the release tags coordinated across the reaction platform.
The QA for the release of this version of reaction-platform should involve testing that the projects are compatible and work together.
Running this release-candidate branch of reaction-platform should also set up the associated release branch for each of the projects in the platform. These are the versions that should be tested - that they are performing as expected, and that they are compatible with each other.
v2.0.0-rc.10
v2.0.0-rc.10
This is our second official release candidate for this project.
Testing Notes
The config.mk file to use the release tags coordinated across the reaction platform.
The QA for the release of this version of reaction-platform should involve testing that the projects are compatible and work together.
Running this release-candidate branch of reaction-platform should also set up the associated release branch for each of the projects in the platform. These are the versions that should be tested - that they are performing as expected, and that they are compatible with each other.
v2.0.0-rc.9
v2.0.0-rc.9
This is our first official release candidate for this project. We're now synchronizing releases across each system that makes up the Reaction Platform. We're starting with v2.0.0-rc.9 because the longest running project reaction is at that version.
This project should be considered pre-release until we've released the final 2.0.0 version.
Using this version will by default use v2.0.0-rc.9 of reactioncommerce/reaction, reactioncommerce/reaction-next-starterkit and reactioncommerce/reaction-hydra for new projects.