"latest" packages #281

Open
opened 2025-12-30 01:23:09 +01:00 by adam · 1 comment
Owner

Originally created by @bioball on GitHub (Feb 21, 2025).

Provide a way to use the "latest" version of a package, where, the version is queried during eval.

Imagined syntax:

import "package://example.com/foo@1.+#/myModule.pkl"

Or, when as a dependency:

amends "pkl:Project"

dependencies {
  ["foo"] { uri = "package://example.com/foo@1.+" }
}

Some thoughts:

  1. Projects with "latest" dependencies should be prevented from being published as packages
  2. The "latest" should only be applied to the minor version or below, because the major version is part of the package identifier.

This requires a package index that can be queried.

Originally created by @bioball on GitHub (Feb 21, 2025). Provide a way to use the "latest" version of a package, where, the version is queried during eval. Imagined syntax: ```pkl import "package://example.com/foo@1.+#/myModule.pkl" ``` Or, when as a dependency: ```pkl amends "pkl:Project" dependencies { ["foo"] { uri = "package://example.com/foo@1.+" } } ``` Some thoughts: 1. Projects with "latest" dependencies should be prevented from being published as packages 2. The "latest" should only be applied to the minor version or below, because the major version is part of the package identifier. This requires a package index that can be queried.
Author
Owner

@StefMa commented on GitHub (Feb 21, 2025):

Simar issue:
https://github.com/apple/pkl/issues/278

Because I guess such dependencies shouldn't be in cache since they can be updated at any time... 🤔

Another which might be related:
#313

Not sure exactly 🤷‍♂️ but all of those somehow match together and might take into account when implementing this.

@StefMa commented on GitHub (Feb 21, 2025): Simar issue: https://github.com/apple/pkl/issues/278 Because I guess such dependencies shouldn't be in cache since they can be updated at any time... 🤔 Another which might be related: #313 Not sure exactly 🤷‍♂️ but all of those somehow match together and might take into account when implementing this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pkl#281