Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jam update buildpack action uses out of date jam version #277

Closed
fg-j opened this issue May 11, 2021 · 2 comments · Fixed by #300
Closed

jam update buildpack action uses out of date jam version #277

fg-j opened this issue May 11, 2021 · 2 comments · Fixed by #300
Assignees

Comments

@fg-j
Copy link

fg-j commented May 11, 2021

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.

@sophiewigmore
Copy link
Member

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.

@sophiewigmore
Copy link
Member

sophiewigmore commented May 27, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants