7d68c25c97
chore: upgrade node to v24.13 ( #13291 )
...
- upgrade node to v24.13
Co-authored-by: Sojan Jose <sojan@pepalo.com >
2026-01-15 20:28:13 -08:00
Vishnu Narayanan and GitHub
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
Sojan Jose and GitHub
fdd35ff549
chore: Update Codespaces ( #11621 )
...
- Fix issues with the current Chatwoot development codespaces
- Switch from webpacket to vite
- Add additional configs to make the development easier with codespaces
- toggles v4 feature true as default
2025-05-29 01:45:00 -06:00
Sojan Jose and GitHub
bc42aec68e
chore: upgrade ruby version to 3.4.4 ( #11524 )
...
- Chore upgrade ruby version to 3.4.4 before we migrate to rails 7.2
over #11037
2025-05-21 19:40:07 +05:30
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 and GitHub
91dd92e318
feat: switch to postgres docker images with pgvector support (v4.0) ( #10658 )
...
Starting v4.0, pgvector support is mandatory. This PR adds pgvector
support for new docker installations.
- Switch to postgres images with pgvector support
- Change the default postgres version from `12` to `16`
2025-01-14 19:45:42 +05:30
31bcdaa3dd
chore: Upgrade ruby to 3.3.3 ( #9664 )
...
- Upgrade the ruby version to 3.3.3
---------
Co-authored-by: Vishnu Narayanan <iamwishnu@gmail.com >
2024-07-05 12:20:07 +05:30
4958b3e7b6
chore: Fix codespaces not booting up ( #8264 )
...
Fixed an issue where the codespace was not correctly booting up.
Fixes #7609
Co-authored-by: Liam Ashdown <liam.ashdown@debbiesvillas.co.uk >
Co-authored-by: Sojan <sojan@pepalo.com >
2024-01-16 14:34:23 +04:00
Sojan Jose and GitHub
ab54d9c629
chore: Upgrade rails and ruby versions ( #2400 )
...
ruby version: 3.0.2
rails version: 6.1.4
2021-08-03 20:11:52 +05:30
Sojan Jose and GitHub
1f02c09a41
chore: Setup dev env with Github Codespaces [alpha] ( #1282 )
...
Easily spin up a Chatwoot development environment with Github Codespaces.
2020-12-09 17:01:28 +05:30
