Skip to content

chore: version packages - #249

Merged
AKogut merged 1 commit into
mainfrom
changeset-release/main
Aug 18, 2026
Merged

chore: version packages#249
AKogut merged 1 commit into
mainfrom
changeset-release/main

Conversation

@AKogut

@AKogut AKogut commented Aug 5, 2026

Copy link
Copy Markdown
Owner

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@flakemetry/cli@0.2.0

Minor Changes

  • fc7f57f: Add run, flaky and doctor. flakemetry run -- pnpm test wraps a test command, uploads the results afterwards and exits with the command's own code — an upload problem warns but never turns a green build red. flakemetry flaky lists the flaky board from the terminal (--json for scripting, --quarantined to filter), and flakemetry doctor reports the configuration, connectivity and what the token is allowed to do, with the token redacted. Both query commands need a token with the read scope.

  • 6c2680d: 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 <testId> 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.

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0
    • @flakemetry/sdk@0.2.1

@flakemetry/contracts@0.2.0

Minor Changes

  • 6c2680d: 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 <testId> 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.

@flakemetry/core@0.1.1

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0

@flakemetry/jest-reporter@0.1.3

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0
    • @flakemetry/sdk@0.2.1

@flakemetry/playwright-reporter@0.1.2

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0
    • @flakemetry/sdk@0.2.1

@flakemetry/sdk@0.2.1

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0
    • @flakemetry/core@0.1.1

@flakemetry/vitest-reporter@0.1.2

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0
    • @flakemetry/sdk@0.2.1

@flakemetry/api@0.0.2

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0
    • @flakemetry/queries@0.0.2
    • @flakemetry/storage@0.0.2

@flakemetry/web@0.0.2

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0
    • @flakemetry/core@0.1.1
    • @flakemetry/queries@0.0.2
    • @flakemetry/storage@0.0.2

@flakemetry/worker@0.0.2

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0
    • @flakemetry/ai@0.0.2
    • @flakemetry/core@0.1.1
    • @flakemetry/queries@0.0.2
    • @flakemetry/storage@0.0.2

@flakemetry/ai@0.0.2

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0

@flakemetry/queries@0.0.2

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0
    • @flakemetry/ai@0.0.2
    • @flakemetry/core@0.1.1

@flakemetry/storage@0.0.2

Patch Changes

  • Updated dependencies [6c2680d]
    • @flakemetry/contracts@0.2.0

@AKogut
AKogut force-pushed the changeset-release/main branch 4 times, most recently from b7deb68 to ead22c2 Compare August 5, 2026 16:30
@AKogut
AKogut force-pushed the changeset-release/main branch from ead22c2 to 79e824a Compare August 18, 2026 08:06
@AKogut
AKogut force-pushed the changeset-release/main branch from 79e824a to 1b3fbb7 Compare August 18, 2026 08:13
AKogut added a commit that referenced this pull request Aug 18, 2026
Found while working out whether the release PR (#249) was safe to merge.
It is not, yet.

#254 changed two **published** packages and shipped no changeset:

```
packages/contracts/src/common.ts       TOKEN_SCOPES gains `quarantine`
packages/contracts/src/{ingestion,query,rest}.ts
packages/cli/src/commands/quarantine.ts
```

#249 was cut before that landed, so merging it as-is publishes
`@flakemetry/cli@0.2.0` with a changelog describing only
`run`/`flaky`/`doctor`, and publishes **nothing** for contracts.

The second half is the part that matters. `@flakemetry/contracts` on npm
would keep a `TokenScope` union of `'ingest' | 'read'` while the API
happily accepts `quarantine` — so anyone typing against the published
package gets a compile error for a scope the server supports, and
nothing anywhere would explain why.

This adds the changeset. The release bot will fold it into #249, which
can then publish both packages together and describe what actually
changed.
@AKogut
AKogut force-pushed the changeset-release/main branch 2 times, most recently from 7641ca6 to 2ed1bdc Compare August 18, 2026 08:18
@AKogut
AKogut force-pushed the changeset-release/main branch from 2ed1bdc to c16bf57 Compare August 18, 2026 08:21
@AKogut
AKogut merged commit def4b1c into main Aug 18, 2026
8 checks passed
@AKogut
AKogut deleted the changeset-release/main branch August 18, 2026 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant