Skip to content

fix: remove corporate-specific URLs from test fixtures#45

Merged
CodeWithJuber merged 1 commit into
masterfrom
claude/forge-work-system-setup-p26ka5
Jul 8, 2026
Merged

fix: remove corporate-specific URLs from test fixtures#45
CodeWithJuber merged 1 commit into
masterfrom
claude/forge-work-system-setup-p26ka5

Conversation

@CodeWithJuber

@CodeWithJuber CodeWithJuber commented Jul 8, 2026

Copy link
Copy Markdown
Owner

What & why

Replace employer-specific gateway URLs and scenario names in test/providers.test.js with generic example.com equivalents. Five occurrences of a corporate domain were present in test fixtures from the provider-detection work in PR #44 — this removes them for privacy.

  • https://api-eu1.aigateway..grouphttps://api.aigateway.example.com
  • "scenario" / "env" → "corporate gateway scenario" / "corporate gateway env"

Checklist

  • npm test passes (Node 18/20/22)
  • npm run check passes (Biome lint + format)
  • New public functions have a test
  • Conventional commit message (feat:/fix:/docs: …)
  • CHANGELOG.md updated under ## [Unreleased]
  • No new runtime dependency (dev deps ok)
  • Substrate/docs updated if this changes forge substrate, forge impact, router/gate, or MCP substrate tools

Risk & rollback

  • Risk level: low
  • Rollback plan: revert the single commit — test URLs are cosmetic, no behavior change

Extra checks (tick if applicable)

  • npm run typecheck passes
  • Logs contain no secrets/PII
  • If AI-assisted: I understand it, verified the package APIs, and it has tests

Generated by Claude Code

Swap employer-specific gateway URLs and scenario names in provider
tests with generic example.com equivalents for privacy.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019PXuKmJp92Gdo2FudNjSx2
@CodeWithJuber CodeWithJuber marked this pull request as ready for review July 8, 2026 20:03
@CodeWithJuber CodeWithJuber merged commit 4778054 into master Jul 8, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants