| Thanks Tobias!
Regarding the deploy jobs: we now have multiple packages to publish from the main repo. I’m not sure how to handle the dependencies between those packages (sprotty > sprotty-protocol, sprotty-elk > sprotty-protocol). Ideally, when we publish next versions, we should also update the version number in the dependencies list. Do you have an idea how to do that?
Regards Miro
Hi, no objects regarding a 0.11.0 release! For GLSP we rather often consume the next versions of sprotty instead of the latest release. So for us the automated next publishing is rather convenient and we would like to keep it. I can have a look at the failing build.
Best Regards Hi Sprotty devs,
I manually published new next versions (0.11.0-next.ddf634c) of sprotty, sprotty-protocol and sprotty-elk. If you have some time, it would be great if you could test these. If there are no objections, I’ll publish v0.11.0 within the next days.
Do we still want the automatic publishing of next versions, or is it sufficient to publish them manually on demand? I’m ok with both approaches.
Regards
-- Dr. Miro Spönemann General Manager / Software Architect TypeFox GmbH Am Germaniahafen 1, 24143 Kiel https://www.typefox.ioTel.: +49 151 42679459 Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385 Geschäftsführer: Daniel Dietrich, Dr. Miro Spönemann
sprotty-dev mailing list
sprotty-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sprotty-dev
-- Tobias Ortmayr
Software Engineer EclipseSource Austria
EclipseSource Services GmbH Schwindgasse 20 / 2-3 1040 Wien
General Manager: Dr. Philip Langer Registered Office: Schwindgasse 20 / 2-3, 1040 Wien; Handelsgericht Wien, FN 421413a
_______________________________________________ sprotty-dev mailing list sprotty-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sprotty-dev
|
