-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v2.0.0 rc.12 #547
Merged
Merged
Release v2.0.0 rc.12 #547
Conversation
This file contains 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
Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
chore: ignore snyk js-yaml vuln for 30 days
Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
resolves: #519 Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
circleci Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
…or-cases Always send a response to logout requests
Signed-off-by: Aldair Cruz <aldaircruz@users.noreply.github.com>
docs: Fix minor typo on README.md
Signed-off-by: Eric Dobbertin <eric@dairystatedesigns.com>
…ed-fields feat: remove unused fields from GQL query
Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
Also changed everything apollo related to semver ~ ranges. Otherwise new versions cause test failures. (Invariant Violation: Ambiguous GraphQL document: contains 2 operations) Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
…nyk-js-yaml chore: update yarn.lock to resolve snyk js-yaml vuln
fix: prettier config was in the wrong place
- Don't take unexpected minor releases - Next commit will bump versions to match yarn.lock Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
- Add fresh yarn.lock file Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
Switch to semver ~1.2.3 style ranges
Signed-off-by: Jeffrey Corpuz <jeffcorpuz@icloud.com>
Signed-off-by: Jeffrey Corpuz <jeffcorpuz@icloud.com>
fix: change calibre ci step to use npx
Signed-off-by: Machiko Yasuda <machiko@reactioncommerce.com>
chore(license): match license from LICENSE.md and README
…duction API Signed-off-by: Machiko Yasuda <machiko@reactioncommerce.com>
Signed-off-by: Machiko Yasuda <machiko@reactioncommerce.com>
docs(README): add instructions on how to run starterkit w/ prod API
Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
…-part-2 chore: change pinned deps to ~ ranges
chore(development): fix debugger command in README
Signed-off-by: Peter Lyons <pete@reactioncommerce.com>
chore: only run snyk when package.json changes
Signed-off-by: Will Lopez <will.lopez77@gmail.com>
…omponents fix: de-duplicate styled-components package
Signed-off-by: Spencer Norman <spencern@gmail.com>
…duction-warning docs: remove production warning
…eta endpoint, updated name in README/docs. Signed-off-by: Nat Hamilton <info@nathamilton.com>
Signed-off-by: Nat Hamilton <info@nathamilton.com>
Signed-off-by: Nat Hamilton <info@nathamilton.com>
…ncommerce/reaction-next-starterkit into chore-476-nnnnat-rename-project
…-project chore: rename project to example-storefront
Signed-off-by: Chris Potter <chris@reactioncommerce.com>
removes fossa status from readme
Signed-off-by: Jeffrey Corpuz <jeffcorpuz@icloud.com>
…version chore: update CHANGELOG, bump version to rc 12
…version chore: update CHANGELOG, bump version to rc 12 Signed-off-by: Jeffrey Corpuz <jeffcorpuz@icloud.com>
…mmerce/example-storefront into release-v.2.0.0-rc.12 Signed-off-by: Jeffrey Corpuz <jeffcorpuz@icloud.com>
Signed-off-by: Spencer Norman <spencern@gmail.com>
Signed-off-by: Spencer Norman <spencern@gmail.com>
Signed-off-by: Spencer Norman <spencern@gmail.com>
spencern
approved these changes
Jul 2, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ready to go.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release v2.0.0-rc.12
This is our fourth release candidate for this project. While this project is technically still
pre-release
until we've released the final 2.0.0 version, it's the most stable version of Reaction Commerce, and we recommend starting new projects with it at this point. See #487 (comment) for more detail on this.This version should be used with
v2.0.0-rc.12
of https://github.com/reactioncommerce/reactionHighlights
We have renamed this project from
reaction-next-starterkit
toexample-storefront
to better convey the intent behind our creating it. We’re also updating our docs to clarify this change.The GraphQL API in reaction v2.0.0-rc.12 has been changed from
/graphql-alpha
tographql-beta
to indicate the increased stability of the API. We think there are still some breaking changes to come in the next 3-6 months to the GraphQL API which is why we're keeping the-beta
suffix for now. As you find bugs with that API, please file issues in the reaction repo.Improvements
Feature
Fix
Chore
Docs