SC/A 2024.1.30 has been released – it is a small b...
# suitecommerce
s
SC/A 2024.1.30 has been released – it is a small bug-fix release. As an FYI we are changing the version numbering system - so .3 becomes .30. This is because of a change in the internal tool we use to track code changes (so do not worry if you think you have missed 27 minor releases).
šŸ‘ 3
One thing you'll notice, when you download the code, is that we slightly changed the structure of the source so that third_parties is now at the same level as the other folders, eliminating the need for a parent folder. So, you'll need make a few adjustments to your version control if you're tracking it.
e
Are you aware of an issue that was preventing to deploy a custom module from 2024.1? is that the bug-fix?
s
I'm not aware of that
e
Do you mind just taking a look? Case: 5941757, defect: 784530
s
The issue work hasn't begun yet. I just did a deploy of 2024.1.30 with no customisations with no problems. Just looking at your setup:
- Node 20.10.0
- npm - 10.2.3
- gulp
-- CLI - 3.0.0
-- Local - unknown
I am using • Node 20.11.1 • npm 10.8.2 • Gulp CLI 3.0.0 • Gulp Local 4.0.2 And part of me thinks you might be a little out of date. I find it odd that when you check the Gulp version it says "unknown" for local.
e
Ha! Thanks for the heads-up, it is not me but someone from the team. I will pass this feedback!
s
Strictly speaking, they're using the right versions as documented
e
I see, yeah they mentioned that one folder does not get created when running
gulp deploy
but it was before this new minor version released. I will tell them to try with this one.
s
I just wonder if the tools actually installed correctly; that's my big thought right now
-gulp v returning "unknown" for local is odd
e
I do not usually check that but I will keep it on mind. I will come back with some feedback
@Steve Goldberg thanks for sharing your environment setup. The gulp local version was the problem! šŸ¤
s
Great. Please make sure your colleague tells the support rep what the problem was, and to close the case and issue
e
For sure!