Skip to content

v1.1.1

Latest

Choose a tag to compare

@github-actions github-actions released this 16 Nov 22:45

The first release on npm. @vol-a/core, @vol-a/lookups, @vol-a/server,
@vol-a/client, @vol-a/react and @vol-a/cli are published to npm from this version on
(pnpm add @vol-a/client); 1.0.0, 1.0.1 and 1.1.0 exist only as tags, images and GitHub
releases. Since 1.1.0: @jsudc/* 0.3, one command for the whole test suite, a footer that
says which release and build a page is, and the production sites https://vol-a.com and
https://examples.vol-a.com. Nothing changes on the wire, in the CLI or in configuration.

Added

  • pnpm test:full: test:cov and test:e2e in one command with one merged coverage
    report (tools/test-full.mjs), the command thilo.toml [testing] names for the board's
    Testing engine (docs/CONTRIBUTING.md).
  • Production of the website: https://vol-a.com is apps/website, built by
    deploy/website/prod.sh with its nginx vhost
    (docs/DEPLOYMENT.md).
  • The website says how fresh it is. The footer of every page, the docs' included, shows
    the version, the date of its release tag, when the site was built (UTC) and the commit;
    the Packages table has an On npm column with the date each package's newest version
    was published there, and that version when it is not the repository's (not on npm yet
    while a package has never been published). Read once per build
    (apps/website/src/build-info.mjs); the registry never fails the build, and SITE_NPM=off
    builds without asking it (apps/website/README.md).
  • Running without the image is documented: node dist/server.js and node dist/worker.js
    of a built checkout as two services, and what the image would otherwise set
    (docs/DEPLOYMENT.md).
    https://examples.vol-a.com, the production examples site, runs that way
    (deploy/examples/prod.sh, two systemd user units); the website's "live examples" links
    now open it.

Changed

  • @jsudc/* 0.3 (@jsudc/core 0.3.0, @jsudc/server 0.3.0, @jsudc/react 0.3.1, the
    lookups and row_link release) in @vol-a/server, @vol-a/client, @vol-a/react, the
    examples site and the website. Nothing changes on the wire: the files collection's rows,
    filters, cursors and GET /vola/udc/subscribe are as before. @jsudc/server 0.3 checks
    at startup that every lookup field names a served collection; vola's kind,
    encryption and processing_status are lookups into lookups.yaml, which name none, so
    @vol-a/server turns that check off and runs it itself without them (udc/links.ts):
    any other lookup or row_link of the registry still stops the start when it does not
    fit. @jsudc/server 0.3 still has no transport for capabilities.subscribe, so vola's
    own stays (docs/REALTIME.md).
  • @vol-a/react's @jsudc/core and @jsudc/react peer ranges are ^0.2.0 || ^0.3.0
    (were ^0.2.0): an application embedding it can stay on @jsudc/* 0.2 or move to 0.3,
    with @jsudc/react and @jsudc/core from the same line. The tutorial program
    (apps/tutorial/ticket-desk) stays on 0.2, because its chapters show its
    package.json.

Docker: docker pull ghcr.io/digital-cube/jsvola:1.1.1
npm: pnpm add @vol-a/client@1.1.1 · @vol-a/react · @vol-a/server · @vol-a/cli · @vol-a/core · @vol-a/lookups