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

chore: release v4.0.0 #688

Closed
wants to merge 2 commits into from
Closed

chore: release v4.0.0 #688

wants to merge 2 commits into from

Conversation

willopez
Copy link
Member

@willopez willopez commented Jun 17, 2020

v.4.0.0

Refactors

  • refactor: Configure react-testing-library and remove unnecessary testing dependencies #686

This is a major update that introduces the following refactors in PR #667

  • Use React hooks for various parts of the application including orders, cart, shop, translations and more. This refactor remove various HOC that added unnecessary complexity to the app.
  • React context is now used and all previous uses of MobX have been removed. Using React context greatly simplifies local states management.
  • Simple translation helpers have been added to support multi-lingual shops. See the useTranslation React hook for more details.
  • Next.js has been update to use version 9.4.1, which includes support for SSG(Static Site Generation). By default product pages are re-regenerated every two minutes. Further, various other features, such as dynamic routes and API routes are now used, either a dynamic route or API
    as appropriate.
  • Various components form the Reaction component library have been removed in favor of using the new Reaction Catalyst design system. This is a stepping stone towards consolidating styling solutions use use only one.

Signed-off-by: Will Lopez <will.lopez@mailchimp.com>
@willopez willopez requested review from rosshadden, manueldelreal and mikemurray and removed request for rosshadden June 17, 2020 23:04
@janus-reith
Copy link
Collaborator

janus-reith commented Jun 29, 2020

This needs to be fixed first: #691

@janus-reith
Copy link
Collaborator

I wonder if v3.2.0 is a suitable version number, considering all the major changes.

As the decision was made to release the projects independently and not necessarily keep version numbers the same across them, that would be v4.0.0 as the next major.

@janus-reith
Copy link
Collaborator

As @manueldelreal pointed out, this should probably be merged before a release: #705

@ghost
Copy link

ghost commented Jul 28, 2020

I've opened up a few issues which block this realease. I'd also lobby strongly for #704 before 3.2.0 is released unless there's a beta period of some sort. If that's standard please ignore. I just started looking at this project two days ago.

Signed-off-by: Mike Murray <hellomikemurray@gmail.com>
@mikemurray mikemurray changed the title chore: release v3.2.0 chore: release v4.0.0 Jul 28, 2020
@mikemurray
Copy link
Member

@janus-reith Agreed. Bumped to 4.0.0

@janus-reith
Copy link
Collaborator

janus-reith commented Jul 29, 2020

Great to hear @mikemurray !

I just noticed that release-next-v3.2.0 doesn't contain all latest commits of trunk, so we should make sure to check this before a release: release-next-v3.2.0...trunk

@janus-reith
Copy link
Collaborator

janus-reith commented Jul 30, 2020

I'd like to upgrade nextjs to v9.5.1 where all the remaining new features we use are now marked as stable before the release: #715

@kieckhafer
Copy link
Member

Closing in favor of #729

@kieckhafer kieckhafer closed this Sep 25, 2020
@nnnnat nnnnat deleted the release-next-v3.2.0 branch November 20, 2020 16:02
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.

None yet

4 participants