Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sprotty-dev] Release Candidate for v0.11.0
AFAIK the inter-repository dependencies are not updated after each next release. e.g. in Theia the inter-repository dependencies always remain at the current release number.
Lerna resolves local dependencies first before using npm as fallback so everybody that checksout the repo still  has the correct state.
Also lerna has a built-in feature to publish a new next (preminor) version of all packages of the repository at once. In this process the inter-package dependencies will be updated as well.
So if eg. sprotty depends on sprotty-protocol in version 10.0.0 in the local repo, then the dependency will automatically be  resolved to 0.11.0-next-<commithash in the package published to npm.
All we have to do is configure lerna in the same fashion as e.g. Theia and introduce a dedicated command for publishing next packages (c.f. https://github.com/eclipse-theia/theia/blob/82c847d43034e37472f626fc5844692c38be0786/package.json#L75)

On Mon, Nov 22, 2021 at 3:40 PM Miro Spönemann <miro.spoenemann@xxxxxxxxxx> wrote:
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


On 22. Nov 2021, at 14:04, Tobias Ortmayr <tortmayr@xxxxxxxxxxxxxxxxx> wrote:

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

On Mon, Nov 22, 2021 at 12:41 PM Miro Spönemann <miro.spoenemann@xxxxxxxxxx> wrote:
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.

The deploy jobs are currently broken: https://ci.eclipse.org/sprotty/
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.io
Tel.: +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@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sprotty-dev

_______________________________________________
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

Back to the top