summarylogtreecommitdiffstats
AgeCommit message (Collapse)Author
17 hoursBump version to 0.6.3Tuure
3 daysUse latest node againTuure
v23.2 was unable to build, but now v23.3 is out which fixes the regression.
7 daysRevert removal of node v23.2 workaroundTuure
I was too quick, this still errors out Still use v23.1 until it settles
7 daysRevert node v23.2 workaroundTuure
v23.2 now works: https://github.com/nodejs/node/issues/55826
10 daysBump version to 0.6.2 and workaround node v23.2.0 regressionTuure
When using latest note (v23.2.0), the build would error out with ``` Unexpected end of JSON input ``` Issue: https://github.com/nodejs/node/issues/55826 Explicitly using v23.1.0 is a workaround.
2024-11-02Bump version to 0.6.1Tuure
2024-09-06Bump version to 0.6.0Tuure
2024-08-29Bump version to 0.5.1Tuure
2024-08-28Bump version to 0.5.0Tuure
2024-08-26Bump version to 0.4.0Tuure
2024-08-06Bump version to 0.3.1Tuure
2024-08-01Bump version to 0.3.0Tuure
2024-07-26Improve `viv --version` outputTuure
2024-07-26Bump version to 0.2.1Tuure
As a side effect, fixes `viv --version`
2024-07-21Bump version to 0.2.0 and rework buildTuure
2024-07-11Fix licenseTuure
2024-05-06Bump versionTuure
2024-04-30Bump versionTuure
2024-01-15Bump versionTuure
2023-12-04Bump versionTuure
2023-12-04Bump version and fix broken vivify-server binTuure
The 'strip unneeded symbols' step would break something, issue related to https://github.com/vercel/pkg Project now has license
2023-11-30Simplify pathTuure
2023-11-30Remove bad install lineTuure
The README.md with the package name as filename didn't make sense in /usr/share/doc, picked that up from an example. I think the README is not needed in doc at all.
2023-11-30Initial commitTuure