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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix path for packages in package.json used for Docker image #16141

Merged
merged 2 commits into from Oct 24, 2022
Merged

Fix path for packages in package.json used for Docker image #16141

merged 2 commits into from Oct 24, 2022

Conversation

paescuj
Copy link
Member

@paescuj paescuj commented Oct 24, 2022

Description

Due to a recent change in PNPM (pnpm/pnpm#5472) the paths to the tarball of the packages in the package.json file generated by the docker/pack.js script are no longer relative but absolute and therefore dependent on the executing system (in this case the GitHub runner).
This resulted in the tarballs not being found within the Docker image build process because the paths were invalid inside the Docker context.

With the fix provided in this pull request, the release process is going to work again (refs: https://github.com/directus/directus/releases/tag/v9.19.1 & #16083 (comment)).
The fix is backwards-compatible with older PNPM versions.
I've tested it in a forked repository (https://github.com/paescuj/directus/actions/runs/3312870014).

Also included revert of revert of #16083 馃槃

Type of Change

  • Bugfix
  • Improvement
  • New Feature
  • Refactor / codestyle updates
  • Other, please describe:

Requirements Checklist

  • New / updated tests are included
  • All tests are passing locally
  • Performed a self-review of the submitted code

If adding a new feature:

  • Documentation was added/updated. PR:

docker/pack.js Show resolved Hide resolved
@rijkvanzanten rijkvanzanten merged commit 5507ca3 into directus:main Oct 24, 2022
@paescuj paescuj deleted the fix-paths-pack-script branch October 24, 2022 13:49
@rijkvanzanten rijkvanzanten added this to the Next Release milestone Nov 1, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants