Feature/web components#153
Merged
Merged
Conversation
…n game-components port)
…-components port)
…sitionWipe game-components port)
…abel game-components port)
…yScreen game-components port)
…gnetteOverlay game-components port)
…ider game-components port)
…e game-components port)
…ointMarker game-components port)
…ture/web-components
…ture/web-components
… so compare returns 0 for equal clocks
…ive, sub-1, NaN, and huge inputs
…dd-length, and non-hex input
…dupe in-flight fetches
…ader) + demo to @toolcase/phaser-plus
…Mesh + demo to @toolcase/phaser-plus
…ery demo to @toolcase/phaser-plus
…quencer + demo to @toolcase/phaser-plus
…o @toolcase/phaser-plus
…`GameObject` in @toolcase/phaser-plus
…case/phaser-plus
…melinePanel` in @toolcase/phaser-plus
… @toolcase/phaser-plus
…emo for @toolcase/phaser-plus
…lidator in @toolcase/base
…t queries to `BPlusIndex`
…e) to `BPlusIndex`
…) to @toolcase/node
…etplay loopback demo to @toolcase/phaser-plus
…em landing demos for @toolcase/phaser-plus
Migrate taskforge UI to @toolcase/web-components (tc-* tags), drop the bundled taskforge package-lock, and tidy web-components Button/react + dashboard-layout/switch styles. Fix all 3 npm audit advisories via root overrides without downgrading next (npm audit fix --force wanted next 16.2.9 -> 9.3.3): - postcss -> ^8.5.15 (XSS in stringify; forces next's bundled copy) - tsup > esbuild -> ^0.28.1 (Windows dev-server file read; scoped to tsup so vite's safe 0.25.12 stays untouched) npm audit now reports 0 vulnerabilities. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
github-token: token-only HTTPS clone (no username), suited to a token
from a social/web login (gh auth login), a PAT, or an OAuth/app token.
Sent as Authorization: Basic base64("x-access-token:<token>") via
GIT_CONFIG_*, so it never lands in argv or on disk.
ssh-key key_env: supply the private key material through an env var
instead of a key_file path. The daemon materializes it into a 0600
temp file it owns at sync time and removes it afterward — no host-side
staging or chown (the friction key_file hits in a container where the
host-uid key is unreadable by the unprivileged daemon).
Inline auth.key is a parse-time error, same as other inline secrets.
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
1 participant
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.
No description provided.