- 
                Notifications
    You must be signed in to change notification settings 
- Fork 77
Merge release 25.1 into master #888
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
Conversation
… against scrumboxes
…thenticateci Bug Fixes for PDPDEVTOOL-5587: [NSN] vscode - oauth2.0 - add the new command authenticate ci
Merge release/24.2 into dev
UIF TypeScript type declarations for NetSuite release 24.2
Bump versions in dev branch.
Fix UIF 24.2 types
keep dev vscode-extension version 2.1.0
merge release24.2 into dev after vscode-extension v2.0.1 changes
propagate PDPDEVTOOL-5831 update supported versions table to dev
…orage-messages-in-node-cli PDPDEVTOOL-5890: Check and fix Node.js warnings in all flows
pdpsdf-9727-json-schemas
…admes Feature/pdpdevtool 5988 update readmes
… the auth warnings
…ove-the-Option-authid-must-have-a-value-error-when-creating-new-project Bugfix/PDPDEVTOOL-6004: [vscode] Removed the "option --authid must have a value" error message when creating new project
…urrences_tba pdpdevtool 5991 remove occurrences tba
…urrences_tba PDPDEVTOOL-5991 fixed vscode remove auth confirmation message
…TOOL-5947_vscode_extension_remove_see_details_warnings_errors
…ension_remove_see_details_warnings_errors -PDPDEVTOOL-5947 vscode-extension - Remove the See Details button on warnings and errors
Remove schemas package
| #865 Would be nice to work into this for the workspace update with the new changes to test the new  | 
| @HeavenlyEntity This release was planned for some months. | 
| Okay @alisyed-19, most firms are using monorepos especially enterprise companies using NetSuite with the latest SDK practices. So to be able to unit test inside one would be an extreme win. This is currently broken 💥 in monorepos so all builds fail in CI due to this improper use case consideration for the jest config. Do we have any timing on when it can be merged since this have been since December? I allowed you access to edit the PR if needed. | 
No description provided.