chore: add changeset for Railway/reverse-proxy URL fix - #26
Merged
Merged
Conversation
Add patch changeset for PR #25 (Fix localhost redirect URLs on Railway/reverse proxy deployments). Move LOCALHOST_REDIRECT_FIX.md and OPERATOR_CHECKLIST.md to docs/ directory. Co-authored-by: Timchosen Uzua <timchosen@gmail.com>
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
2 participants
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.
Summary
Adds a patch changeset for PR #25 which fixed localhost redirect URLs on Railway/reverse proxy deployments.
PR #25 was merged without a changeset, so npm will not publish the fix. This PR adds the required changeset to trigger a version bump and npm publish.
Changes
@dashcommerce/coredescribing the Railway/reverse-proxy URL fixLOCALHOST_REDIRECT_FIX.mdandOPERATOR_CHECKLIST.mdfrom repo root todocs/directoryChangeset Details
Package:
@dashcommerce/coreVersion bump: patch
Summary: Railway/reverse-proxy: use configured public site URL for Stripe success/cancel and portal return URLs instead of request.origin which can be localhost:PORT
Context
PR #25 implemented
getPublicSiteUrl()helper to fix Stripe redirect URLs and admin invite links that were incorrectly pointing tohttp://localhost:8080instead of the public domain when deployed behind a reverse proxy (Railway, nginx, etc.).The fix ensures URLs are constructed using
ctx.site.url(fromSITE_URLenv var) instead ofrequest.origin.Related
docs/directory