Skip to content

fix(core): opt#16

Merged
Fiona2016 merged 2 commits into
mainfrom
fix/replay-intake-hardcoded-ip
Jul 7, 2026
Merged

fix(core): opt#16
Fiona2016 merged 2 commits into
mainfrom
fix/replay-intake-hardcoded-ip

Conversation

@Fiona2016

@Fiona2016 Fiona2016 commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

The staging/fed-staging intake endpoints were hardcoded to an internal
IP (http://10.99.1.110:11300) directly in `intakeSites.ts`. Since these
constants are publicly exported, the internal IP + plaintext http endpoint
leaked into every published `@flashcatcloud/browser-*` artifact.

Move the staging endpoints to the existing build-time injection mechanism
(`__BUILD_ENV__*` + replace-build-env / webpack DefinePlugin), the same
convention already used for SDK_VERSION. Values are read from the
INTAKE_SITE_STAGING / INTAKE_SITE_FED_STAGING env vars at build time and
default to an empty string, so release artifacts never contain an internal
host. Staging remains configurable by setting the env var at build time.

Verified: `BUILD_MODE=release` build of @flashcatcloud/browser-core emits
`INTAKE_SITE_STAGING = ""` and `grep -r 10.99` over cjs/ and esm/ is clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Fiona2016 Fiona2016 marked this pull request as ready for review July 7, 2026 12:02
Replace the build-time env injection with a hardcoded public https host,
matching the native SDKs (Android FlashcatSite.STAGING / iOS
FlashcatSite.staging both use jira.flashcat.cloud). This keeps the original
audit finding resolved (no internal 10.99.x IP, no cleartext http/port) while
making staging work out of the box across all builds with zero CI wiring, and
keeps the three client SDKs consistent.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Fiona2016 Fiona2016 merged commit c60b632 into main Jul 7, 2026
1 check passed
@Fiona2016 Fiona2016 changed the title fix(core): remove hardcoded internal staging IP from intake sites fix(core): opt Jul 7, 2026
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.

1 participant