1
2
Fork
You've already forked auto-encrypt
3

Fix install failures in CI pipelines running npm >= 7 #1

Closed
syndic-will wants to merge 0 commits from syndic-will:ci-installs into main
pull from: syndic-will:ci-installs
merge into: small-tech:main
small-tech:main
small-tech:ip-address-support
small-tech:ari-fix
small-tech:jose-1.28.2-to-6.1.3-upgrade
small-tech:ARI
small-tech:2.x
First-time contributor
Copy link

Hi Aral,

I'm running into this NPM bug when trying to npm ci in a test pipeline with my apps that depend on auto-encrypt: https://github.com/npm/cli/issues/2610

This started after updating my pacakge & pipeline runners to use node 16 & npm 8

It seems the issue is npm started preferring SSH connections when a dependency is pointing to a public git repo, and the pipeline runners don't have SSH keys setup so they can't fetch the dependency. In this case its aral/bent#errors-with-response-headers

The workaround I found from that thread is to force npm into using https by being explicit in the dependency specification.

Hi Aral, I'm running into this NPM bug when trying to `npm ci` in a test pipeline with my apps that depend on auto-encrypt: https://github.com/npm/cli/issues/2610 This started after updating my pacakge & pipeline runners to use node 16 & npm 8 It seems the issue is npm started preferring SSH connections when a dependency is pointing to a public git repo, and the pipeline runners don't have SSH keys setup so they can't fetch the dependency. In this case its `aral/bent#errors-with-response-headers` The workaround I found from that thread is to force npm into using https by being explicit in the dependency specification.
Author
First-time contributor
Copy link

Here's an example of the error: https://github.com/immers-space/immers/actions/runs/3378969630/jobs/5609903444

And here's a commit where I worked around it temporarily: https://github.com/immers-space/immers/pull/94/commits/a17c630ddd23a9d8e5df86baf5f3842d12fde194

However, the next time I update dependencies, npm will revert that back to git+ssh unless we change it here in auto-encrypt

Here's an example of the error: https://github.com/immers-space/immers/actions/runs/3378969630/jobs/5609903444 And here's a commit where I worked around it temporarily: https://github.com/immers-space/immers/pull/94/commits/a17c630ddd23a9d8e5df86baf5f3842d12fde194 However, the next time I update dependencies, npm will revert that back to `git+ssh` unless we change it here in auto-encrypt
Owner
Copy link

All looks good @syndic-will, just got a clean run in the tests and will merge this now. Thank you for your contribution :)

All looks good @syndic-will, just got a clean run in the tests and will merge this now. Thank you for your contribution :)
Owner
Copy link

@syndic-will I just followed the instructions for doing a manual merge here on Codeberg but it’s not getting picked up as a merge. (This is my first pull request merge here.)

Going to open an issue with Codeberg about it. Apologies for the hassle.

@syndic-will I just followed the instructions for doing a manual merge here on Codeberg but it’s not getting picked up as a merge. (This is my first pull request merge here.) Going to open an issue with Codeberg about it. Apologies for the hassle.
Owner
Copy link

@syndic-will Looks like this is an issue that’s been around for two years?!

Codeberg/Community#438 (comment)

Just pinged them to see what we can do about it as I’d like you to get credit for your pull request :)

@syndic-will Looks like this is an issue that’s been around for two years?! https://codeberg.org/Codeberg/Community/issues/438#issuecomment-664357 Just pinged them to see what we can do about it as I’d like you to get credit for your pull request :)
Author
First-time contributor
Copy link

Closing this as the changes are in. No worries about credit, my commit is in the history anyway

Closing this as the changes are in. No worries about credit, my commit is in the history anyway

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
small-tech/auto-encrypt!1
Reference in a new issue
small-tech/auto-encrypt
No description provided.
Delete branch "syndic-will:ci-installs"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?