Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(gatsby): don't force leading slash for external paths in routes manifest (#38639) #38646

Merged
merged 1 commit into from
Oct 19, 2023

Conversation

gatsbybot
Copy link
Collaborator

Backporting #38639 to the 5.12 release branch

(cherry picked from commit 5dbcf9e)

…anifest (#38639)

* don't force leading slash for external redirects

* add test

* perf: regexp -> double String.startWith checks

---------

Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
(cherry picked from commit 5dbcf9e)
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Oct 19, 2023
@pieh pieh added bot: merge on green Gatsbot will merge these PRs automatically when all tests passes and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Oct 19, 2023
@gatsbybot gatsbybot merged commit 8302bc8 into release/5.12 Oct 19, 2023
1 check failed
@gatsbybot gatsbybot deleted the backport-5.12-38639 branch October 19, 2023 15:34
This was referenced Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: merge on green Gatsbot will merge these PRs automatically when all tests passes type: cherry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants