Have netlify.toml semantics changed? It seems the “publish” path is now expected to be relative to the “base” path.
It seems like one of my sites is grandfathered into old behavior, where the build will succeed if the “publish” path in netlify.toml is absolute, but fails when it’s relative to “base”.
I have another, newly created site from the same git repo that behaves the opposite way. Builds succeed only when the “publish” path in netlify.toml is relative to “base”.
If this is some internal compatibility flag you have enabled for my old site, can Netlify change it so that my old site behaves like all new sites seem to behave? Otherwise, let me know if I’m mistaken. Tried clearing build cache already. I’ve worked around the issue by temporarily removing the path specifications from netlify.toml and specifying them in the UI.
I’m hesitant to provide the site DNS name here publicly until I’m more confident about the cause of the problem.
Thanks for your understanding