chore: version packages - #178
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
roborev: Combined Review (
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 30, 2026 19:45
7c1fb60 to
4d7b452
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
cloudburn@0.13.0
Minor Changes
#166
783e67cThanks @axonstone! - Remove four heuristic AWS rules that could flag valid cost choices without usage evidence: disabled API Gateway caching, missing CloudWatch metric filters, configured Lambda provisioned concurrency, and ungated S3 Intelligent-Tiering. Default scans no longer report those findings, and the unused provider datasets are no longer loaded or exported.#179
442bf8bThanks @axonstone! - Add an AWS cost guardrail that flags budgets forecast to breach their limit before actual spend exceeds it.Patch Changes
783e67c,442bf8b]:@cloudburn/rules@0.29.0
Minor Changes
#166
783e67cThanks @axonstone! - Remove four heuristic AWS rules that could flag valid cost choices without usage evidence: disabled API Gateway caching, missing CloudWatch metric filters, configured Lambda provisioned concurrency, and ungated S3 Intelligent-Tiering. Default scans no longer report those findings, and the unused provider datasets are no longer loaded or exported.#179
442bf8bThanks @axonstone! - Add an AWS cost guardrail that flags budgets forecast to breach their limit before actual spend exceeds it.@cloudburn/sdk@0.29.0
Minor Changes
#166
783e67cThanks @axonstone! - Remove four heuristic AWS rules that could flag valid cost choices without usage evidence: disabled API Gateway caching, missing CloudWatch metric filters, configured Lambda provisioned concurrency, and ungated S3 Intelligent-Tiering. Default scans no longer report those findings, and the unused provider datasets are no longer loaded or exported.#179
442bf8bThanks @axonstone! - Add an AWS cost guardrail that flags budgets forecast to breach their limit before actual spend exceeds it.Patch Changes
783e67c,442bf8b]: