Skip to content
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 52 commits into from
Jul 2, 2019
Merged

Release v2.0.0 rc.12 #547

merged 52 commits into from
Jul 2, 2019

Conversation

jeffcorpuz
Copy link
Contributor

@jeffcorpuz jeffcorpuz commented Jul 1, 2019

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/reaction

Highlights

We have renamed this project from reaction-next-starterkit to example-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 to graphql-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

focusaurus and others added 30 commits April 9, 2019 12:23
chore: ignore snyk js-yaml vuln for 30 days
…or-cases

Always send a response to logout requests
docs: Fix minor typo on README.md
…ed-fields

feat: remove unused fields from GQL query
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 <[email protected]>
…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 <[email protected]>
- Add fresh yarn.lock file

Signed-off-by: Peter Lyons <[email protected]>
Signed-off-by: Jeffrey Corpuz <[email protected]>
Signed-off-by: Jeffrey Corpuz <[email protected]>
fix: change calibre ci step to use npx
chore(license): match license from LICENSE.md and README
Signed-off-by: Machiko Yasuda <[email protected]>
docs(README): add instructions on how to run starterkit w/ prod API
…-part-2

chore: change pinned deps to ~ ranges
focusaurus and others added 19 commits June 17, 2019 16:59
chore(development): fix debugger command in README
chore: only run snyk when package.json changes
…omponents

fix: de-duplicate styled-components package
Signed-off-by: Spencer Norman <[email protected]>
…duction-warning

docs: remove production warning
…eta endpoint, updated name in README/docs.

Signed-off-by: Nat Hamilton <[email protected]>
…ncommerce/reaction-next-starterkit into chore-476-nnnnat-rename-project
…-project

chore: rename project to example-storefront
Signed-off-by: Chris Potter <[email protected]>
…version

chore: update CHANGELOG, bump version to rc 12
…version

chore: update CHANGELOG, bump version to rc 12
Signed-off-by: Jeffrey Corpuz <[email protected]>
Copy link
Contributor

@spencern spencern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ready to go.

@spencern spencern changed the title Release v.2.0.0 rc.12 Release v2.0.0 rc.12 Jul 2, 2019
@jeffcorpuz jeffcorpuz merged commit 9b5d8ac into master Jul 2, 2019
@spencern spencern deleted the release-v.2.0.0-rc.12 branch July 2, 2019 01:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants