Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
None
-
-
stripes-force 145, stripes-force 151
-
Stripes Force
Description
FOLIO uses Yarn v1: https://github.com/folio-org/folio-tools/blob/master/jenkins-slave-docker/Dockerfile.jammy-java-17
Yarn v1 has been deprecated since April 2020: https://yarnpkg.com/advanced/migration , commit
Regarding Yarn v2 the Yarn people "recommend upgrading if possible" for several reasons, including stability: https://yarnpkg.com/getting-started/migration#why-should-you-migrate https://yarnpkg.com/getting-started/qa#why-should-you-upgrade-to-yarn-modern
Currently there are still Yarn v1 releases: https://github.com/yarnpkg/yarn/releases
However, they don't give any statement for how long they will provide security fixes for Yarn v1.
The FOLIO flower release support period is 8 months. We don't know whether Yarn v1 gets supported with security fixes during this time, this puts FOLIO at risk.
We will migrate our build toolchain npm v7 and node 15/16.
TestRail: Results
Attachments
Issue Links
- has to be done after
-
STRIPES-679
SPIKE: investigate yarn v2 vs npm v7
-
- Closed
-
- relates to
-
ESCONF-6
eslint-plugin-react-hooks@"^2.1.2" causes peer-dep inconsistency
-
- Closed
-
-
ESCONF-7
eslint-plugin-import@"2.14.0" causes peer-dep inconsistency
-
- Closed
-
-
STCLI-178
@octokit/rest@"^17.1.4" causes a peer-dep inconsistency
-
- Closed
-
-
STCOM-839
@storybook/addon-actions@"^5.3.19" causes a peer-dep inconsistency
-
- Closed
-
-
STCOM-981 update outdated dependencies
-
- Open
-
-
STCOR-540
@apollo/client@"^3.2.1" from stripes-core@7.2.0 causes a peer-dep inconsistency
-
- Closed
-
-
STCOR-541
redux-observable@"^0.15.0" from stripes-core@7.2.0 causes a peer-dep inconsistency
-
- Closed
-
-
STSMACOM-685 notes depends on react-quill but package.json does not include it
-
- Closed
-
-
UICIRC-575
@folio/stripes-template-editor@"^1.0.0" from ui-circulation@5.0.0 causes multiple peer-dep inconsistencies
-
- Closed
-
-
UICIRC-576
react-codemirror2@"^1.0.0" causes peer-dep inconsistency
-
- Closed
-
-
UICR-135
@folio/plugin-find-user@"^4.0.0" causes peer-dep inconsistency
-
- Closed
-
-
UIF-307
eslint@"^7.7.0" causes peer-dep inconsistency
-
- Closed
-
-
UINV-260
eslint@"^7.9.0" causes peer-dep inconsistency
-
- Closed
-
-
UIORGS-249
eslint@"^7.7.0" causes peer-dep inconsistency
-
- Closed
-
-
UIPFPAT-33
@folio/eslint-config-stripes@"^3.2.0" causes peer-dep inconsistency
-
- Closed
-
-
UIPFU-41
@folio/eslint-config-stripes@"^3.2.0" causes peer-dep inconsistency
-
- Closed
-
-
UIPFU-42
@folio/eslint-config-stripes@"^3.2.0" causes peer-dep inconsistency
-
- Closed
-
-
UITEN-172
@folio/eslint-config-stripes@"^3.2.1" causes peer-dep inconsistency
-
- Closed
-
-
UITEN-173
@folio/eslint-config-stripes@"^3.2.1" causes peer-dep inconsistency
-
- Closed
-
- mentioned in
-
Page Loading...