Skip to content

chore: version packages - #280

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

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

Conversation

@AKogut

@AKogut AKogut commented Aug 18, 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.1

Patch Changes

  • a04f9f7: Stop a broken flakemetry.yml from failing a build, and make the tracker's environment settings work.

    flakemetry run resolved the config before spawning the wrapped command, so an invalid config file raised and the test suite never ran — the wrapper exists precisely so that Flakemetry cannot fail a build. It now warns and carries on. Config errors also arrive as a diagnosis rather than a Node stack trace.

    FLAKEMETRY_TRACKER_ENABLED, FLAKEMETRY_TRACKER_AFTER_DAYS and FLAKEMETRY_TRACKER_RECOVERY_DAYS were documented, passed through both compose files, and read by nothing. They now reach the policy layer like every other setting.

  • Updated dependencies [09519db]

  • Updated dependencies [a04f9f7]

    • @flakemetry/contracts@0.2.1
    • @flakemetry/sdk@0.2.2

@flakemetry/contracts@0.2.1

Patch Changes

  • 09519db: /openapi.json now describes the whole API rather than the read half. It was generated from the read-route table, so ingestion, the quality gate, artifact presigning and quarantine were invisible to anything generating a client — with nothing in the document to say a client was seeing a fraction of it. Request bodies are now included, generated from the same zod schemas the endpoints validate against.

  • a04f9f7: Stop a broken flakemetry.yml from failing a build, and make the tracker's environment settings work.

    flakemetry run resolved the config before spawning the wrapped command, so an invalid config file raised and the test suite never ran — the wrapper exists precisely so that Flakemetry cannot fail a build. It now warns and carries on. Config errors also arrive as a diagnosis rather than a Node stack trace.

    FLAKEMETRY_TRACKER_ENABLED, FLAKEMETRY_TRACKER_AFTER_DAYS and FLAKEMETRY_TRACKER_RECOVERY_DAYS were documented, passed through both compose files, and read by nothing. They now reach the policy layer like every other setting.

@flakemetry/core@0.1.2

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1

@flakemetry/jest-reporter@0.1.4

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1
    • @flakemetry/sdk@0.2.2

@flakemetry/playwright-reporter@0.1.3

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1
    • @flakemetry/sdk@0.2.2

@flakemetry/sdk@0.2.2

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1
    • @flakemetry/core@0.1.2

@flakemetry/vitest-reporter@0.1.3

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1
    • @flakemetry/sdk@0.2.2

@flakemetry/api@0.0.3

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1
    • @flakemetry/queries@0.0.3
    • @flakemetry/storage@0.0.3

@flakemetry/web@0.0.3

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1
    • @flakemetry/core@0.1.2
    • @flakemetry/queries@0.0.3
    • @flakemetry/storage@0.0.3

@flakemetry/worker@0.0.3

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1
    • @flakemetry/ai@0.0.3
    • @flakemetry/core@0.1.2
    • @flakemetry/queries@0.0.3
    • @flakemetry/storage@0.0.3

@flakemetry/ai@0.0.3

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1

@flakemetry/queries@0.0.3

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1
    • @flakemetry/ai@0.0.3
    • @flakemetry/core@0.1.2

@flakemetry/storage@0.0.3

Patch Changes

  • Updated dependencies [09519db]
  • Updated dependencies [a04f9f7]
    • @flakemetry/contracts@0.2.1

@AKogut
AKogut force-pushed the changeset-release/main branch from 9bee44b to 4369884 Compare August 18, 2026 10:17
@AKogut
AKogut force-pushed the changeset-release/main branch from 4369884 to 10e48d4 Compare August 18, 2026 11:47
@AKogut
AKogut merged commit 17770d3 into main Aug 18, 2026
9 checks passed
@AKogut
AKogut deleted the changeset-release/main branch August 18, 2026 12:08
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