Skip to content

Change release process to upload custom edition #14469

@Akirathan

Description

@Akirathan

In #14319 we have investigated that all the library/edition infrastructure present for multiple years still works. #14319 contains description of steps how to upload a custom library to locally hosted library server and use it both from engine runner and from IDE.

The goal of this issue is to demonstrate changes to the nightly release process such that:

  • Add a custom, zipped, library as another artifact to the release
  • Modify buildEngineDistribution task so that it creates another edition file next to distribution/editions/0.0.0-dev.yaml.
  • There is no need to host a separate HTTP library server:
    • The new edition will contain definition of a library repository with the URL to the GH release.
    • JDK can index files within zip/jar archives, so to fetch a manifest,
      • we can use URL of format jar:https://github.com/enso-org/enso/releases/tag/2025.3.1-nightly.2025.12.10!manifest.yaml.
      • as JarURLConnection defines

In other words:

  • Enso_Extra edition will contain a single Foo library
  • This library is hosted on GH, as an artifact on the release.
  • It will be automatically downloaded without need to change package.yaml of a project.

Metadata

Metadata

Assignees

Labels

Projects

Status

⚙️ Design

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions