You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the update buildpack action uses jam 0.9.0. However, the latest is v0.11.0. The update includes a fix introduce in 0.10.1 that enables jam update builder to work when registry path != buildpackage ID.
There's an issue with that fix when used with private registries (see paketo-buildpacks/packit#175), so it might not make sense to upgrade the version yet, but it would be good to have a mechanism that keeps this jam version up to date.
The text was updated successfully, but these errors were encountered:
Note that there exists an update-tools workflow that could possibly be used to keep the jam version in the actions up to date if we add a tools.json file like we have for the builder, implementation, and language family sub directories.
Update: the issue @fg-j mentioned (paketo-buildpacks/packit#175) has been resolved and the fix is available in packit v0.11.1, so we can safely update the version.
Currently, the update buildpack action uses jam 0.9.0. However, the latest is v0.11.0. The update includes a fix introduce in 0.10.1 that enables
jam update builder
to work when registry path != buildpackage ID.There's an issue with that fix when used with private registries (see paketo-buildpacks/packit#175), so it might not make sense to upgrade the version yet, but it would be good to have a mechanism that keeps this jam version up to date.
The text was updated successfully, but these errors were encountered: