chore: version packages - #284
Open
AKogut wants to merge 1 commit into
Open
Conversation
AKogut
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
August 18, 2026 13:21
09b0a3b to
d184489
Compare
AKogut
force-pushed
the
changeset-release/main
branch
from
August 18, 2026 13:33
d184489 to
3b7b26b
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/contracts@0.3.0
Minor Changes
cd50173: The daily LLM token budget is now a per-project policy field. It was read only from the environment, so
ai.dailyTokenBudgetin a project'sflakemetry.ymlwas documented, validated and ignored — one instance could have exactly one budget.eae093b: Move to zod 4. The validation shape on the wire is unchanged —
{ error, issues: [{ path, message }] }— but the messages are more specific: an invalid commit sha now reports the pattern it had to match instead of a bare "Invalid".zod-to-json-schemais gone; zod 4 generates JSON Schema itself, which the OpenAPI document and the API reference now use.@flakemetry/cli@0.2.2
Patch Changes
flakemetry --versionreported0.0.0regardless of the installed version. It now reports the real one, baked in at build time — the version is the first thing anyone is asked for in a bug report, and0.0.0identified nothing.@flakemetry/core@0.1.3
Patch Changes
@flakemetry/jest-reporter@0.1.5
Patch Changes
@flakemetry/playwright-reporter@0.1.4
Patch Changes
@flakemetry/sdk@0.2.3
Patch Changes
@flakemetry/vitest-reporter@0.1.4
Patch Changes
@flakemetry/notify@0.1.0
Minor Changes
ai_budget_spentnotification, sent when a project's daily LLM token budget runs out and root-cause analysis pauses. Subscribe on any channel — Slack, Discord, email or a signed webhook. Deduplicated per project per day, since the budget is re-checked on every run.@flakemetry/api@0.0.4
Patch Changes
@flakemetry/web@0.0.4
Patch Changes
@flakemetry/worker@0.0.4
Patch Changes
@flakemetry/ai@0.0.4
Patch Changes
eae093b: Move to zod 4. The validation shape on the wire is unchanged —
{ error, issues: [{ path, message }] }— but the messages are more specific: an invalid commit sha now reports the pattern it had to match instead of a bare "Invalid".zod-to-json-schemais gone; zod 4 generates JSON Schema itself, which the OpenAPI document and the API reference now use.Updated dependencies [cd50173]
Updated dependencies [eae093b]
@flakemetry/queries@0.0.4
Patch Changes
@flakemetry/storage@0.0.4
Patch Changes