-
Notifications
You must be signed in to change notification settings - Fork 37
Version 2.8.0 vs 2.7.0 #255
Comments
@froucher hmm, maybe there is a mismatch between the build for development/testing and the production build? |
Yes, I also reproduce the issue with master branch, it seems the issue started with the version 2.7.1, maybe it is a npm dependency issue, I think I am close to find why it is happening... |
It seems the issue starts with this commit: 0a9cfab Because I rollbacked commits one by one until the previous commit fbca8bd, redo the npm install for "event-stream" old dependency, and it started to work again. And if I move my local again to 0a9cfab commit and redo the npm install, then the issue comes back. I will continue to investigate why "merge-stream" dependency is not working. |
@froucher Can you please try the fix/parse-input branch? |
This fix is working fine!! 👏 👏 👏 There's no difference between both package.xml |
Piping a git diff to `force-dev-tool changeset create` led to wrong results and was printing `readable not null`. Fixes #255
🎉 This issue has been resolved in version 2.8.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Hi @amtrack,
I am checking the last version (
2.8.0
) of force-dev-tool, and I have a weird issue.The issue is that
package.xml
with2.8.0
has a lot of less elements that thepackage.xml
generate with2.7.0
version and when I execute thechangeset create delta
with2.8.0
the console shows a lot of lines like:It is weird because the changeset is created without
ApexClass
,ApexPage
,ApexTrigger
,Compact Layout
, and many others metadata that are currently supported.I updated my local node version to
12
but the issue continues, and when I launch functional tests it is all green.I am going to continue investigating why it is happening.., but any idea of why it is happening is welcome.
Thanks.
The text was updated successfully, but these errors were encountered: