From 816786a3bde39a75367a24f5f07fa63d24347e97 Mon Sep 17 00:00:00 2001 From: Andrii Kohut Date: Tue, 18 Aug 2026 10:06:31 +0200 Subject: [PATCH] chore: cover the quarantine scope with a changeset MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit packages/contracts and packages/cli both changed in #254 with nothing to release them. Left alone, the pending release publishes the CLI while the contracts package stays at a version whose TokenScope union has no `quarantine` in it — so an API that accepts the scope and a published type that does not know it exist at the same time. --- .changeset/quarantine-scope.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 .changeset/quarantine-scope.md diff --git a/.changeset/quarantine-scope.md b/.changeset/quarantine-scope.md new file mode 100644 index 0000000..4b9ec1f --- /dev/null +++ b/.changeset/quarantine-scope.md @@ -0,0 +1,10 @@ +--- +'@flakemetry/contracts': minor +'@flakemetry/cli': minor +--- + +Add the `quarantine` token scope and `flakemetry quarantine`. + +`TOKEN_SCOPES` gains a third entry alongside `ingest` and `read`. It is separate because it is the one call that can stop a failing test from blocking a build, and that should be granted deliberately rather than arriving with the ability to read. Anything narrowing a `TokenScope` union will see the new member. + +`flakemetry quarantine ` holds a test in or out of quarantine by hand, and `--auto` hands it back to the scorer. A decision made this way is not overwritten on the next run.