Repository navigation
Point the Console submodule at the merged billing sweep - #271
Closed
matuscongrady wants to merge 3 commits into
Closed
matuscongrady wants to merge 3 commits into
matuscongrady wants to merge 3 commits into
Conversation
Co-Authored-By: Claude Fable 5.1 <[email protected]>
# Conflicts: # apps/console
Contributor
Author
|
Not needed: main's Console pointer already includes the merged billing sweep (console-app#73) through later pointer updates. |
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.
Submodule pointer for console-app #73, the billing fault sweep (S53). No public file changes: the registry's S53 entries did not change.
The Console branch now carries the latest Console
mainmerged in. The merge needed two adjustments inbilling-database.test.ts: thetenanthelper keeps main's cost-seeding parameter and gains the optional organization ID the custom-pricing scenario needs, and the multi-region scenario registers its two MiniStack regions with the fixture'sDescribeRegions(main's attribution handler reads regions from there now) and restores the shared customer account afterwards so main's unreachable-region scenario still finds its stack.Checks after the merge: billing lane 33/33,
console-api368 Bun + 15 Node,console-api-2typecheck,console-fast-rules9,console-offline-contracts7,console-support-template(cfn-lint, pre-existing W3005),pnpm test:tools86,pnpm check:integrated. CI is switched off; merge together with the Console PR.🤖 Generated with Claude Code