chore: version packages - #280
Merged
Merged
Conversation
AKogut
force-pushed
the
changeset-release/main
branch
from
August 18, 2026 10:17
9bee44b to
4369884
Compare
AKogut
force-pushed
the
changeset-release/main
branch
from
August 18, 2026 11:47
4369884 to
10e48d4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.ymlfrom failing a build, and make the tracker's environment settings work.flakemetry runresolved 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_DAYSandFLAKEMETRY_TRACKER_RECOVERY_DAYSwere 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
Patch Changes
09519db:
/openapi.jsonnow 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.ymlfrom failing a build, and make the tracker's environment settings work.flakemetry runresolved 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_DAYSandFLAKEMETRY_TRACKER_RECOVERY_DAYSwere 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
@flakemetry/jest-reporter@0.1.4
Patch Changes
@flakemetry/playwright-reporter@0.1.3
Patch Changes
@flakemetry/sdk@0.2.2
Patch Changes
@flakemetry/vitest-reporter@0.1.3
Patch Changes
@flakemetry/api@0.0.3
Patch Changes
@flakemetry/web@0.0.3
Patch Changes
@flakemetry/worker@0.0.3
Patch Changes
@flakemetry/ai@0.0.3
Patch Changes
@flakemetry/queries@0.0.3
Patch Changes
@flakemetry/storage@0.0.3
Patch Changes