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

Version 1.12.6 #336

Merged
merged 2 commits into from
May 24, 2024
Merged

Version 1.12.6 #336

merged 2 commits into from
May 24, 2024

Conversation

nmanu1
Copy link
Contributor

@nmanu1 nmanu1 commented May 24, 2024

Fixes

nmanu1 and others added 2 commits May 24, 2024 14:46
This PR pins `gettext-extractor` to a minor version (v3.6) prior to [v3.7.1](https://github.com/lukasgeiter/gettext-extractor/releases/tag/v3.7.1) that was released with a change that breaks Jambo upgrades performed with Node 12 and npm 6. That change added support for TS v5 and removed support for older TS versions. When upgrading Jambo via the code editor, the version of `gettext-extractor` was being updated to the latest version, which would in turn upgrade to the latest version of TS (v5.4.5) in the acceptable range (4-5). But, v5.4.5 of TS requires Node 14 or higher, causing an error when using `engine-strict=true` in the `.npmrc`. Also, because the code editor by default uses Node 12 and npm 6, we can't use `overrides` in the package.json (which was released in npm 8) to pin the transitive TS dep to v4.

J=WAT-4073
TEST=manual

Tried locally pointing the Theme to my local Jambo repo and saw that install was successful with `engine-strict=true`, when it gives the same error reported in the Slack thread when trying to force install an older version of Jambo.
@coveralls
Copy link

Coverage Status

coverage: 47.814%. remained the same
when pulling 6c9080a on hotfix/v1.12.6
into ab560e0 on master.

@nmanu1 nmanu1 merged commit fbfb68a into master May 24, 2024
8 checks passed
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.

4 participants