Daniel Rodriguez

After my initial research I did not continue working on it since I did not have a reasonable solution at the time. I should have reverted it to something other...

updating these packages to latest appear to have fixed the problem for me "@itwin/itwinui-react": "^3.12.0", "@types/react": "^18.3.3", "@types/react-dom": "^18.3.0", "react": "^18.3.1", "react-dom": "^18.3.1", I do not know if latest is...

Looks like other platforms are messed up. Will try to address, otherwise will reach out to non windows users for help If I can't figure it out. This built for...

in test three what caused the cherry pick to have conflicts. Also who is notified when conflicts happened and a PR is opened? Is someone auto assigned to the PR?

Changes look fine, and you're tests look good. My only concern is that this is a pretty hefty addition to this pipeline. Does it seem rational to make this its...

> maybe we could add a manual validation step before actually pushing this to npm (unless it's already there). Of course, the validation would be skipped if the script made...

If this gets added we should make sure we properly update libsrc-vendor and libsrc-main branches

@diegoalexdiaz is there anything we need to address in itwinjs-core to use these enhancements? Otherwise I'll only update imodel-native to consume these changes in our 5.0.x branch

completed in the PR referenced above. To my understanding no other changes were needed to utilize this new version of bis core other than updating the version of bis schema...

Scales will not be included as part of MVP. See [here](https://github.com/iTwin/itwinjs-core/issues/8490#issuecomment-3353282156) for original post.