evals-lab 0.1.4 → 0.3.0

package/CHANGELOG.md

@@ -0,0 +1,66 @@
+# Changelog
+
+What changed in each release of evals-lab, for someone who has it installed.
+Newest first. Read a release's **Upgrade notes** before installing it: an
+upgrade can rewrite what the lab keeps in your data directory, and an older
+version cannot always read it back.
+
+## 0.3.0
+
+### Upgrade notes
+
+- **Copy your data directory before upgrading** (see "Where your data is
+  kept" in the README). 0.3.0 changes what it keeps there in a form 0.2.x
+  cannot read. To go back, reinstall 0.2.x and restore the copy.
+- On its first start, 0.3.0 rewrites every stored dataset as dataset version
+  6. The originals are kept in the store as well.
+- Pipelines are read and saved as pipeline version 12.
+- Export JSON now writes dataset version 6, which 0.2.x refuses to import.
+  Import still reads versions 1 to 6.
+- A pipeline file that lists its evals under `tests:` still imports.
+- A plugin that registers `testTypes` still loads. The new name is
+  `evalTypes`.
+
+### Added
+
+- `discarded` metric: passes only when the job's rules discarded the reply.
+- `contains` takes `except`.
+- Add metric asks for the type first, from a list grouped by what the metric
+  checks. Change type… is in each metric's menu.
+- A header over Runs, Library › Datasets and a Source names what is open.
+  Tap the name to switch. Its menu holds the rest of the actions.
+- A loading indicator wherever the page waits, with Retry when a request
+  fails. A list no longer reads as empty while it loads.
+
+### Changed
+
+- Tests are called Evals: Runs › Evals, and the Evals columns in Results
+  and History.
+- A case is an item of its dataset's Source, plus the metrics a good reply
+  passes. A dataset names its Source.
+- Library › Datasets is one view. The table shows Item, Status (Graded, To do
+  or Missing), Metrics and Note. Add case picks from the Source's items that
+  have no case yet. Change item… is in the case's menu.
+- An eval that names a dataset grades each item by that case's metrics. The
+  separate `case` metric is gone, and is dropped from older pipelines.
+- Contains, Contains any and Contains all match a list reply item by item,
+  and say what they found, missed and invented.
+- Ignore case now applies item by item. A new Contains metric starts with it
+  on. A dataset's existing metrics are set to it, as they always matched
+  that way. A pipeline's keep what you set.
+- A metric of weight 0 is watched: listed under Watch in Results, never
+  scored. Results shows one verdict per eval.
+- A Source's Upload replaces Add files.
+- Rename is a dialog for datasets, as it is for pipelines.
+- Every tab has the dotted background, not Home alone.
+- History opens faster: the list loads without each run's full replies, and
+  the server compresses what it sends.
+
+### Fixed
+
+- History showed one row for two runs queued in the same second.
+
+### Removed
+
+- Map against Source, and the map run in Runs › Mapping. A case matches its
+  item by exact name.

package/README.md

@@ -126,6 +126,43 @@ at `127.0.0.1` reloads the page at `localhost`, the address registered above,
 and carries on from there. Anything open in the tab, such as an Add source
 dialog, does not carry over.
 
+## Google Drive
+
+**Not usable yet.** The lab can sign in to Google Drive, but nothing reads
+from Drive yet: a Source made from a Drive folder is still to come. Until it
+arrives, there is no reason to set up a Google app, and the steps below are
+provisional. They haven't been tried against a real Google project.
+
+When it arrives, the sign-in will be held by the lab's server, on your
+machine. It will reach only the files you pick: the lab asks for
+`drive.file` access, never your whole Drive.
+
+To sign in, open **Setup › Connections**, then use the Google Drive row's
+menu › **Sign in**. If the row says *Not Configured*, give the lab a Google
+app first, once:
+
+1. At <https://console.cloud.google.com>, make a project. Enable the
+   **Google Drive API** and the **Google Picker API**.
+2. **OAuth consent screen:** choose *External*. Give the app a name and your
+   email, add the scope `.../auth/drive.file`, then **Publish app**. It needs
+   no review from Google, because that scope is non-sensitive. Left in
+   *Testing*, a sign-in lapses after 7 days.
+3. **Credentials › Create credentials › OAuth client ID**, of type
+   **Desktop app**. Download its JSON file.
+4. **Credentials › Create credentials › API key.** Restrict it to the Google
+   Picker API.
+5. In the lab, use the Google Drive row's menu › **Configure…**, then
+   **Load client file…**, and choose the file from step 3. Paste the key
+   from step 4 into **API key**.
+
+A Desktop app needs no redirect registered: Google sends the browser back to
+any port on this machine. A lab you reach at its own address, from another
+machine, needs a *Web application* client instead. Choose that type in
+Configure…, then register the **Redirect URI** it shows with the client.
+
+Everything saves as you type. The client's secret is kept by the lab and
+never shown again. The window says only that one is saved.
+
 ## Reaching it from another machine
 
 By default only your own machine can reach the lab. That is deliberate: the
@@ -138,6 +175,12 @@ lab holds your API keys.
 
 ## Upgrading and removing
 
+Read `CHANGELOG.md` in the package, or on
+<https://www.npmjs.com/package/evals-lab?activeTab=code>, before upgrading.
+Its **Upgrade notes** say when a release rewrites what is in your data
+directory in a form an older version cannot read; copy the directory first
+if you may want to go back.
+
 ```bash
 npm install -g evals-lab@latest   # upgrade
 npm uninstall -g evals-lab        # remove; your data directory stays

package/lab/VERSION

@@ -1 +1 @@
-0.1.4 (2026.10.01-291)
+0.3.0 (2026.10.02-355)