Age | Commit message (Collapse) | Author | |
---|---|---|---|
3 days | Bump version to 0.6.3 | Tuure | |
6 days | Use latest node again | Tuure | |
v23.2 was unable to build, but now v23.3 is out which fixes the regression. | |||
10 days | Revert removal of node v23.2 workaround | Tuure | |
I was too quick, this still errors out Still use v23.1 until it settles | |||
10 days | Revert node v23.2 workaround | Tuure | |
v23.2 now works: https://github.com/nodejs/node/issues/55826 | |||
13 days | Bump version to 0.6.2 and workaround node v23.2.0 regression | Tuure | |
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-02 | Bump version to 0.6.1 | Tuure | |
2024-09-06 | Bump version to 0.6.0 | Tuure | |
2024-08-29 | Bump version to 0.5.1 | Tuure | |
2024-08-28 | Bump version to 0.5.0 | Tuure | |
2024-08-26 | Bump version to 0.4.0 | Tuure | |
2024-08-06 | Bump version to 0.3.1 | Tuure | |
2024-08-01 | Bump version to 0.3.0 | Tuure | |
2024-07-26 | Improve `viv --version` output | Tuure | |
2024-07-26 | Bump version to 0.2.1 | Tuure | |
As a side effect, fixes `viv --version` | |||
2024-07-21 | Bump version to 0.2.0 and rework build | Tuure | |
2024-07-11 | Fix license | Tuure | |
2024-05-06 | Bump version | Tuure | |
2024-04-30 | Bump version | Tuure | |
2024-01-15 | Bump version | Tuure | |
2023-12-04 | Bump version | Tuure | |
2023-12-04 | Bump version and fix broken vivify-server bin | Tuure | |
The 'strip unneeded symbols' step would break something, issue related to https://github.com/vercel/pkg Project now has license | |||
2023-11-30 | Simplify path | Tuure | |
2023-11-30 | Remove bad install line | Tuure | |
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-30 | Initial commit | Tuure | |