8 Commits

Author	SHA1	Message	Date
gabrieljablonski	6ab1898992	Merge branch 'main' into chore/merge-upstream-4.10	2026-01-16 14:01:53 -03:00
Vishnu Narayanan	ab83a663f0	chore: upgrade node to 24.x LTS (#13004) ... Upgrade node to `24.12` LTS FIxes https://github.com/chatwoot/chatwoot/issues/12546 Fixes https://linear.app/chatwoot/issue/CW-5707/nodejs-23-reached-eol	2026-01-12 18:10:23 +05:30
gabrieljablonski	339271b93e	chore: update workflows to trigger on tags instead of branches	2025-05-06 17:03:53 -03:00
Gabriel Jablonski	65430e4633	Merge branch 'fazer-ai/main' into chore/merge-upstream	2025-04-09 19:22:12 -03:00
Bruno Shiohei	4304e06748	fix: Updating the Ubuntu version to run the tests (#11260) ... In my previous PR I got some errors that when checking it is possible to conclude that the version of ubuntu 20.04 in the Github Actions images to run the tests is no longer supported.  Possible to check at this url: https://github.com/actions/runner-images/issues/11101 ## What's changed Changing the Ubuntu version in the image to run the tests. Old version: 20.04 New version: 22.04 ## BEFORE:  ## NOW: 	2025-04-08 16:36:06 -07:00
Gabriel Jablonski	e930820f68	ci: update workflow to trigger on fazer-ai/main branch and remove from PRs (#17) ... * ci: update workflow to trigger on fazer-ai/main branch and remove from PRs * ci: update workflows to trigger on fazer-ai/main branch and enable manual dispatch	2025-04-03 23:28:38 -03:00
Shivam Mishra	f2a7e1da6b	fix: Corepack pnpm issue (#10840) ... So, a while back Circle CI builds and Heroku builds started to fail. From all the threads I read, it seems like the [npm registry rotated it's signing keys](https://github.com/pnpm/pnpm/issues/9014#issuecomment-2616589753) New pnpm versions were signed with the new key. Corepack, however, bundles a static set of trusted keys (from Node’s release), so it continued verifying signatures only against the old key. When it encountered packages signed with the new key, Corepack’s integrity check failed with “Cannot find matching keyid” errors.This mismatch caused Corepack’s integrity check to fail with “Cannot find matching keyid” errors. Workarounds include the following 1. Updating Corepack (to 0.31.0), they [upgraded their package](https://github.com/nodejs/corepack/releases/tag/v0.31.0) to include the new integrity check keys. But we seldom control what's going on with the CI, also, updating this across our scripts is going to be a painful task. Besides Heroku has [made some fixes](https://github.com/heroku/buildpacks-nodejs/pull/1010) around this 2. Disabling integrity checks 🔥 #YOLO 3. Pinning `pnpm` to older versions, or pinning it to a newer version with the checksum in place. Doing the third one here, running `corepack use pnpm@9.15.5` fixes this, [ref](https://github.com/pnpm/pnpm/issues/9014#issuecomment-2623761494) We can get rid of this over time as CDN caches used by build systems are refreshed. But the change in this PR is not disruptive in anyway, only rigidly secure. Fixes: https://github.com/chatwoot/chatwoot/issues/10832 --- Here are the threads to follow - https://github.com/pnpm/pnpm/issues/9014 - https://github.com/pnpm/pnpm/issues/9029 - https://github.com/nodejs/corepack/issues/612 - https://github.com/nodejs/corepack/issues/616 - https://github.com/heroku/buildpacks-nodejs/pull/1010 --------- Co-authored-by: Vishnu Narayanan <vishnu@chatwoot.com>	2025-02-05 10:12:29 -08:00
Vishnu Narayanan	ee02923ace	chore: fix circleci on vite build (#10214) ... - Switch to pnpm based build - Switch circleci from docker to machine to have more memory - Fix frontend and backend tests Fixes https://linear.app/chatwoot/issue/CW-3610/fix-circle-ci-for-vite-build --------- Co-authored-by: Shivam Mishra <scm.mymail@gmail.com> Co-authored-by: Pranav <pranavrajs@gmail.com> Co-authored-by: Pranav <pranav@chatwoot.com>	2024-10-07 15:27:41 +05:30