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(release): fix default renderer resolution to be relative within t… #22331
fix(release): fix default renderer resolution to be relative within t… #22331
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit d4c8b27. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to double check snapshot changes
b11b753
to
d90c4d9
Compare
d90c4d9
to
3c1333d
Compare
3c1333d
to
d4c8b27
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
…he package
Current Behavior
The default renderer is specified as an absolute path which can get resolved to a different version of Nx.
For the nx repo, this is the typescript code.
Expected Behavior
The default renderer is specified as a relative path which is always within the same package release is being run with.
Related Issue(s)
Fixes #