Conversation
Bumps [react-virtuoso](https://github.com/petyosi/react-virtuoso/tree/HEAD/packages/react-virtuoso) from 4.13.0 to 4.18.3. - [Release notes](https://github.com/petyosi/react-virtuoso/releases) - [Changelog](https://github.com/petyosi/react-virtuoso/blob/master/packages/react-virtuoso/CHANGELOG.md) - [Commits](https://github.com/petyosi/react-virtuoso/commits/react-virtuoso@4.18.3/packages/react-virtuoso) --- updated-dependencies: - dependency-name: react-virtuoso dependency-version: 4.18.3 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [vite-plugin-top-level-await](https://github.com/Menci/vite-plugin-top-level-await) from 1.5.0 to 1.6.0. - [Commits](Menci/vite-plugin-top-level-await@v1.5.0...v1.6.0) --- updated-dependencies: - dependency-name: vite-plugin-top-level-await dependency-version: 1.6.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…8089) - New /logs edge function with service_role-only auth - Uses @clickhouse/client-web for parameterized queries - Commands: query (filtered log search), stats (namespace/service counts) - ClickHouse creds via ExternalSecrets + SealedSecret (RBAC-managed) - Creds flow: SealedSecret → clickhouse-logs → ExternalSecret → supabase-shared → deployment env
Contributor
Author
Dependency ReviewThe following issues were found:
|
…t-virtuoso-4.18.3' into dev
…-plugin-top-level-await-1.6.0' into dev # Conflicts: # pnpm-lock.yaml
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Bumps [tailwind-merge](https://github.com/dcastil/tailwind-merge) from 2.5.4 to 3.5.0. - [Release notes](https://github.com/dcastil/tailwind-merge/releases) - [Commits](dcastil/tailwind-merge@v2.5.4...v3.5.0) --- updated-dependencies: - dependency-name: tailwind-merge dependency-version: 3.5.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [react-virtualized-auto-sizer](https://github.com/bvaughn/react-virtualized-auto-sizer) from 1.0.26 to 2.0.3. - [Release notes](https://github.com/bvaughn/react-virtualized-auto-sizer/releases) - [Changelog](https://github.com/bvaughn/react-virtualized-auto-sizer/blob/main/CHANGELOG.md) - [Commits](bvaughn/react-virtualized-auto-sizer@1.0.26...2.0.3) --- updated-dependencies: - dependency-name: react-virtualized-auto-sizer dependency-version: 2.0.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…wind-merge-3.5.0' into dev # Conflicts: # pnpm-lock.yaml
…t-virtualized-auto-sizer-2.0.3' into dev # Conflicts: # pnpm-lock.yaml
Bumps [react-force-graph](https://github.com/vasturiano/react-force-graph) from 1.47.6 to 1.48.2. - [Commits](vasturiano/react-force-graph@v1.47.6...v1.48.2) --- updated-dependencies: - dependency-name: react-force-graph dependency-version: 1.48.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…t-force-graph-1.48.2' into dev # Conflicts: # pnpm-lock.yaml
* fix(astro): rename slug to ref across proto/schema/MDX to fix Starlight routing Starlight hijacks the frontmatter `slug` field as a route override, causing items like /alchemist-stardust/ instead of /itemdb/alchemist-stardust/. Rename the proto field to `ref` throughout the chain: proto definitions, generated Zod schemas, all 153 MDX frontmatter entries, API route handlers, content config validation, and the discordsh itemdb data file. OSRS slug fields are unchanged (separate system). * fix(codegen): regenerate .binpb descriptors with slug->ref rename * fix(rust): rename slug->ref across bevy crates and axum-kbve Update prost-generated proto structs (Item, Npc, Quest, QuestChain, Zone, Region, WorldObjectDef, PointOfInterest) and all registry/json code that accesses the field. Methods renamed: from_slug->from_ref, get_by_slug->get_by_ref, id_for_slug->id_for_ref. Also update axum-kbve profile.rs JSON key fallback.
* fix(discordsh): stabilize flaky multiple_fire_flasks_stack_burning test Bump test enemy HP to 500 and guard against enemy flee (all level tiers have Flee in their intent pool). The test validates burning effect stacking, not flee behavior, so it gracefully skips the burning assertion if the enemy fled between fire flask uses. * feat(bevy_battle): add snapshot module for render-ready combat state Add bevy_battle::snapshot with CombatSnapshot, PlayerSnapshot, EnemySnapshot, and EffectSnapshot types. The capture() function extracts a game-agnostic combat snapshot from the ECS world that any renderer (SVG cards, isometric HUD, web UI) can consume. 6 new tests covering player/enemy capture, effects, death detection, index sorting, defending flag, and clone/debug traits. * feat(discordsh): wire CombatSnapshot into SVG card rendering pipeline Add snapshot capture to CombatTurnResult and GameCardTemplate::from_snapshot() that reads combat fields (HP, armor, effects, intent) from bevy_battle's ECS snapshot while preserving session fields (gold, XP, gear, room, phase). This establishes a single source of truth for combat display data across SVG cards, isometric game, and future web UI renderers. * fix(discordsh): update proto field access from slug to ref Align with upstream proto rename (slug → ref) across itemdb, npcdb, mapdb, and questdb schemas. Updates id_for_slug → id_for_ref, from_slug → from_ref, and .slug → .r#ref field access.
Verify Starlight pages are served at correct nested paths (/itemdb/beer/, /mapdb/coal-vein/, etc.) and NOT at root level. Also tests JSON API endpoints return valid data with ref field instead of slug. Catches routing regressions like the slug-override bug.
…8094) Replace hardcoded route lists with dynamic discovery from the container's own sitemap-index.xml and JSON API endpoints. Tests now automatically cover new content without code changes. - Fetch sitemap, sample routes per DB prefix, verify 200 + HTML - Pull refs from /api/*.json, verify routes resolve and use ref - Confirm items are not served at root level via API-driven refs
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.
Release: Dev → Main
18 atomic commits ready for main
Features
0f6199f)46fb2fb)eb795ee)Bug Fixes
2154d51)Tests
6d99c21)Chores
8c5ab2a)7ddd5c3)9453b3d)6df4a1e)1dafa52)deb0284)bce7d95)Other Changes
614a5e5)c08bf92)56d6642)3c35310)04187ca)f141be5)This PR is automatically maintained by CI — KBVE Studio