chore(deps-dev): bump ajv from 6.12.6 to 6.14.0 in /web#2
Merged
Conversation
Bumps [ajv](https://github.com/ajv-validator/ajv) from 6.12.6 to 6.14.0. - [Release notes](https://github.com/ajv-validator/ajv/releases) - [Commits](ajv-validator/ajv@v6.12.6...v6.14.0) --- updated-dependencies: - dependency-name: ajv dependency-version: 6.14.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
vamsiramakrishnan
pushed a commit
to vamsiramakrishnan/scion
that referenced
this pull request
Mar 29, 2026
… command Progress During scion start (#1 DX pain): - Add ProgressFunc callback to StartOptions (api/types.go) - Wire 5 progress steps through agent Start flow: "Preparing workspace..." → "Resolving credentials..." → "Checking container image..." → "Pulling image..." → "Starting container..." - CLI displays each step as it happens (cmd/common.go) - Add "Waiting for agent to initialize..." before tmux polling - Eliminates the 10-30 second silence that made users think CLI was hung - JSON output mode suppresses progress (clean machine output) Delete Confirmation (GoogleCloudPlatform#2 DX pain): - Add confirmation prompt before local agent deletion: "Delete 2 agent(s) (including git branches): agent-a, agent-b" "Are you sure? [y/N]" - Default is NO (safe by default) - --force / -f flag skips confirmation for scripts - JSON output mode skips confirmation (scripting compatibility) - Shows branch warning when --preserve-branch is NOT set Actionable Error Messages: - tmux timeout error now includes troubleshooting steps: "Check container logs: scion logs <name>" "Verify image exists: docker images | grep scion" "Check Docker is running: docker info" scion status Command: - New `scion status` — single health dashboard like `git status` - Shows: container runtime (version), image registry, credentials - Shows: current grove context with path - Shows: running agents with color-coded status indicators - Shows: contextual hints when things are missing - Green checkmarks for healthy, red crosses with fix commands for broken https://claude.ai/code/session_01TDLLMgpR2ZbfyPzgYqnJ1k
vamsiramakrishnan
pushed a commit
to vamsiramakrishnan/scion
that referenced
this pull request
Mar 29, 2026
GoogleCloudPlatform#2 — Auto-tail hints after detached start: - Show "Tip: Attach with: scion attach <name>" and "Tip: View logs with: scion logs <name> --follow" after detached start - Eliminates "did it work?" anxiety for the most common usage pattern GoogleCloudPlatform#3+6 — Empty state hints in scion list: - When no agents found, show actionable getting-started commands: "Get started: scion start my-agent 'task' --attach" "Browse templates: scion templates list" "Install tools: scion marketplace list" GoogleCloudPlatform#4 — Hub graceful fallback: - Detect connection refused / no such host / timeout errors specifically - Show clear remediation: check Hub is running, use --no-hub flag, or scion hub disable - Differentiate auth failures from connectivity failures GoogleCloudPlatform#5 — Optimized Dockerfile (Dockerfile.fast): - Ubuntu 24.04 base with git-core PPA (Git >= 2.47 from packages) - Downloads Go binary instead of compiling from source - Single apt-get layer for all runtime dependencies - Estimated build time: ~3 minutes (vs ~15 minutes for source compile) - Usage: docker build -f Dockerfile.fast -t core-base:latest GoogleCloudPlatform#7 — UUID-free output: - Remove UUID from agent start success message - Was: "Agent 'x' launched successfully (ID: f47ac10b-58cc-...)" - Now: "Agent 'x' launched successfully." GoogleCloudPlatform#8 — Jargon glossary in scion --help: - Add "Key Concepts" section explaining grove, agent, template, harness, and profile in plain language - Add "Getting Started" section with 4 essential commands - First thing new users see when running scion --help GoogleCloudPlatform#9 — scion doctor --fix: - New --fix flag for auto-remediation - Checks and fixes: machine init, image registry, credentials, grove context, shell completions - Green checkmarks for healthy, warnings with fix commands for broken - Runs config checks BEFORE system checks when --fix is enabled GoogleCloudPlatform#10 — Gemini extension manifest generation: - marketplace install now generates gemini-extension.json alongside Claude settings.json and Gemini settings.json - Creates ~/.gemini/extensions/<name>/gemini-extension.json - Manifest includes name, version, mcpServers config - Compatible with `gemini extensions install` format https://claude.ai/code/session_01TDLLMgpR2ZbfyPzgYqnJ1k
This was referenced Apr 10, 2026
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.
Bumps ajv from 6.12.6 to 6.14.0.
Commits
e3af0a76.14.0b552ed6add regExp option to address $data exploit via a regular expression (CVE-2025...72f2286docs: update v7 info231e52bMerge pull request #1320 from philsturgeon/patch-1d3475fcAdd spectral, an AJV util from a sponsor413afe0docs: v7.0.0-beta.311e997bupdate readme for v7Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.