This repository has been archived by the owner on Jul 12, 2023. It is now read-only.
Releases: guardian/discussion-rendering
Releases · guardian/discussion-rendering
v15.0.0
v14.0.0
Major Changes
-
d0721e7: Update project to React 18:
- Update
react
,react-dom
& corresponding types. - Use the new
react-dom
createRoot
syntax for rendering - Upgrade @guardian dependencies to latest version, including source-react-components v13 which is on React 18
- Upgrade @testing-library dependencies to support React 18
- Upgrade Typescript to v4.9.5
- Update
v13.0.0
Major Changes
-
bcd2a21: This release introduces a change in its peer dependencies, which is a always a
breaking change.- @guardian/libs@^12.0.0 (from ^10.0.0)
Consumers should consider upgrading their local versions of libs, which only
brings two major changes:
v12.0.0
Major Changes
-
22c1d98: ### What
Add required propidApiUrl
to the discussion App. The url is coming from CAPI and passed via DCR.Why
The previous version of discussion-rendering had the prod identity url hardcoded and was hitting this regardless of environment. This was causing CORS errors when trying to post a comment as
https://m.code.dev-theguardian.com/
is not one of the allowed domains to hit the prod api.How to consume
This change handles the consumption of
idApiUrl
by the application.
v11.0.3
Drop sourcemap
- fix: drop source maps from build 18ac401
- Merge pull request #635 from guardian/dependabot/npm_and_yarn/babel/plugin-transform-runtime-7.19.6 cc47821
- chore(deps-dev): bump @babel/plugin-transform-runtime f5cccb7
- Merge pull request #639 from guardian/dependabot/npm_and_yarn/rollup-3.2.5 417ca71
- chore(deps-dev): bump rollup from 2.79.1 to 3.2.5 1900224