Skip to content
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

Update to monaco 0.45 #290

Merged
merged 10 commits into from
Jan 3, 2024
Merged

Update to monaco 0.45 #290

merged 10 commits into from
Jan 3, 2024

Conversation

CGNonofr
Copy link
Contributor

@CGNonofr CGNonofr commented Dec 7, 2023

published as 1.85.0-next.0

also fix #289

@CGNonofr CGNonofr mentioned this pull request Dec 7, 2023
@kaisalmen
Copy link
Collaborator

@CGNonofr awesome PR on release day of new VSCode. 🎉 Can you please release a preview version for testing. I will take a look at everything tomorrow morning.

I have one request/discussion point about the versioning scheme.
Example: Upgrade from 1.83.12 to 1.83.16 seems like a patch, but you know it wasn't. If I use ~1.83.12 as version selector in a dependent project you expect non-breaking changes. The only way to prevent this right now is to pin-point it to something like 1.83.12.

What do you think about the following version scheme:
185.0.0 = [vscode-version].[mva-level-changes].[mva-bugfixes]

So, new features, breaking changes will be 185.1.0, and bug fixes 185.0.1 like in regular semantic versioning. The meaning of minor is a bit stretched here, but there is at least the possibility to distinguish.

@CGNonofr
Copy link
Contributor Author

CGNonofr commented Dec 7, 2023

I have the feeling someone didn't read the description (:

It looks like a great idea! Do you mind creating an issue or a discussion?

@kaisalmen
Copy link
Collaborator

It looks like a great idea! Do you mind creating an issue or a discussion?

Will do...

@kaisalmen
Copy link
Collaborator

See: #291

@kaisalmen
Copy link
Collaborator

@CGNonofr did local tests. First impression is good. Can you please produce a preview release? Thank you.

@CGNonofr
Copy link
Contributor Author

CGNonofr commented Dec 8, 2023

@CGNonofr did local tests. First impression is good. Can you please produce a preview release? Thank you.

You mean a next version? It's already done

@kaisalmen
Copy link
Collaborator

You mean a next version? It's already done

Sorry, overlooked that.

@CompuIves
Copy link
Collaborator

I'll install this version on our codebase and see if everything works. I'll probably know by Monday!

@CompuIves
Copy link
Collaborator

But don't let me block the merge. If there's anything that need changing I can contribute them after as well.

@CGNonofr
Copy link
Contributor Author

@kaisalmen => abae48a

@kaisalmen
Copy link
Collaborator

Latest finding form tests with preview version of TypeFox/monaco-languageclient#584 createConfiguredDiffEditor seems to be broken.

@CompuIves
Copy link
Collaborator

Upgrade was pretty smooth! Everything is working as expected here. The only hurdle was updating our xterm dependencies to @xterm/xterm and their respective versions. Other than that the upgrade went smoothly.

@CGNonofr
Copy link
Contributor Author

CGNonofr commented Jan 2, 2024

Latest finding form tests with preview version of TypeFox/monaco-languageclient#584 createConfiguredDiffEditor seems to be broken.

=> 576b108 (no idea why it wasn't an issue before nor the exact source of the issue, I've failed debugging it - there is a lot of events handlers and callbacks I was unable to follow - before I noticed that difference)

@kaisalmen
Copy link
Collaborator

@CGNonofr happy new year! 🎇 Thank you for finding this. With monaco-editor 0.44.0 they switched to a the new DiffEditor implementation, right.? Maybe this error is somehow related/follow-up problem (this is wild guessing, though).

If you release a new next version, I can verify it with our dependent library stack and then we can merge that in hopefully today.

@CGNonofr
Copy link
Contributor Author

CGNonofr commented Jan 3, 2024

@CGNonofr happy new year! 🎇 Thank you for finding this. With monaco-editor 0.44.0 they switched to a the new DiffEditor implementation, right.? Maybe this error is somehow related/follow-up problem (this is wild guessing, though).

If you release a new next version, I can verify it with our dependent library stack and then we can merge that in hopefully today.

Happy new year (:

You're probably right 🤷

published as 1.85.0-next.2 :)

Copy link
Collaborator

@kaisalmen kaisalmen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good now. Did extensive testing with dependent repos/examples! LGTM

@CGNonofr
Copy link
Contributor Author

CGNonofr commented Jan 3, 2024

It looks good now. Did extensive testing with dependent repos/examples! LGTM

awesome! thanks for the time spent!

@CGNonofr CGNonofr merged commit aa1dbe1 into main Jan 3, 2024
1 check passed
@CGNonofr CGNonofr deleted the update-monaco-0.45 branch January 3, 2024 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Demo Page
3 participants