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

fix GitHub Action floating deps scenario for PNPM #10425

Merged

Conversation

jelhan
Copy link
Contributor

@jelhan jelhan commented Jan 8, 2024

The Floating Dependencies scenario is broken for a newly created Ember addon using PNPM. This change fixes it.

It seems that wyvox/action-setup-pnpm's no-lockfile option is not working as expected. It throws the following error:

Error: Dependencies lock file is not found in /home/runner/work/test-ember-addon-with-pnpm/test-ember-addon-with-pnpm. Supported file patterns: pnpm-lock.yaml

The option has been removed in wyvox/action-setup-pnpm@v3. So upgrading is not an option. But using --no-lockfile flag of PNPM is the recommended upgrade path anyways: wyvox/action-setup-pnpm#3

Please find a demonstration of the bug here: https://github.com/jelhan/test-ember-addon-with-pnpm/actions/runs/7453402485/job/20278700434

A demonstration that the fix work could be found here: jelhan/test-ember-addon-with-pnpm#1

@NullVoxPopuli would be great if you could review. I think you are the expert here as you implemented the PNPM support in Ember CLI and maintain wyvox/action-setup-pnpm.

@NullVoxPopuli
Copy link
Contributor

yeah, the things you call out are exactly the motivation for the change in v3 👍

So upgrading is not an option.

Upgrading to v3 should done (probably as separate PR), as there are important fixes in there (specifically around determining what tooling versions to use, based on your package.json (inherited upstream by way of upgrading setup-node and configuring it))

@NullVoxPopuli NullVoxPopuli merged commit f824a6a into ember-cli:master Jan 8, 2024
11 checks passed
@jelhan
Copy link
Contributor Author

jelhan commented Jan 8, 2024

Thanks a lot for quick review.

So upgrading is not an option.

Upgrading to v3 should done (probably as separate PR), as there are important fixes in there (specifically around determining what tooling versions to use, based on your package.json (inherited upstream by way of upgrading setup-node and configuring it))

Sorry. I phrased it badly. I meant, upgrading is not an option to fix this bug. The changes landed with this PR unlock the upgrade. The upgrade to wyvox/action-setup-pnpm@v3 should only require bumping the version number now. At least that's what RenovateBot done in my project and it worked find. 😆

@jelhan jelhan deleted the fix-addon-ci-floating-deps-for-pnpm branch January 8, 2024 22:49
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 this pull request may close these issues.

None yet

2 participants