fix(railway): drop admin-only platformFeatureFlags from selections - #543
Open
BlankParticle wants to merge 1 commit into
Open
fix(railway): drop admin-only platformFeatureFlags from selections#543BlankParticle wants to merge 1 commit into
BlankParticle wants to merge 1 commit into
Conversation
Contributor
|
Install the packages built from this commit: Distilled@distilled.cloud/core bun add https://pkg.ing/@distilled.cloud/core/477cd22@distilled.cloud/railway bun add https://pkg.ing/@distilled.cloud/railway/477cd22 |
Railway CLI login-session (browserless / `railway login`) tokens cannot read the admin-only `me.platformFeatureFlags` field. Railway rejects the ENTIRE GraphQL query with a blanket `Not Authorized` (HTTP 200 + errors[]), which broke workspace resolution via `me` for every oauth-method profile. Patch drops the field from all four generated selections: me, accessGroupMemberAdd.user, userTermsUpdate, and workspacePolicyDeploySourceAllowlistAdd.addedBy. No consumer needs it.
BlankParticle
force-pushed
the
fix/railway-platform-feature-flags
branch
from
September 3, 2026 21:45
bfd9075 to
477cd22
Compare
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.
Railway CLI login-session tokens (browserless /
railway login, the ones that show up under Sessions in the dashboard) cannot read the admin-onlyme.platformFeatureFlagsfield. Because Railway returns authorization failures asHTTP 200with anerrors[]array, denying one field rejects the entire query with a blanketNot Authorized.The generated
mequery selectedplatformFeatureFlags, so workspace resolution (me { workspace / workspaces }) failed for every account using a CLI-login token — even though the token is otherwise a full account token that can read the workspace, list projects, and deploy.This patch drops the field from all four generated selections that include it:
meaccessGroupMemberAdd(nesteduser)userTermsUpdateworkspacePolicyDeploySourceAllowlistAdd(nestedaddedBy){ "op": "remove", "path": "/shapes/com.railway.api#MeResponse/members/platformFeatureFlags" }No consumer of the field exists. After regeneration
platformFeatureFlagsappears zero times in the SDK, and a live CLI-login token resolves its workspace again.