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

chore: pin more hyper deps #381

Merged
merged 4 commits into from
Nov 17, 2023
Merged

chore: pin more hyper deps #381

merged 4 commits into from
Nov 17, 2023

Conversation

achou11
Copy link
Member

@achou11 achou11 commented Nov 16, 2023

Tomas was dealing with issues because of a mangled lockfile, which updated a transitive dep (hyperblobs) and caused issues in our tests.

This change won't fix that scenario, but just to avoid other potential headaches in the future, pinning any hyper deps that haven't been pinned yet.

@achou11 achou11 requested a review from gmaclennan November 16, 2023 20:10
Copy link
Member

@gmaclennan gmaclennan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, maybe add hyperblobs as a dep too in order to pin it? And try to include this in the release to avoid issues

@achou11 achou11 force-pushed the ac/pin-more-hyper-deps branch from 5d82eb5 to e702291 Compare November 17, 2023 14:44
@achou11 achou11 merged commit 526d257 into main Nov 17, 2023
7 checks passed
@achou11 achou11 deleted the ac/pin-more-hyper-deps branch November 17, 2023 14:54
gmaclennan added a commit that referenced this pull request Nov 20, 2023
* main:
  chore: pin more hyper deps (#381)
  chore: extract and test construction of icon url (#366)
  chore: fix release workflow configuration (#379)
  chore: remove unused/unneeded deps (#376)
  chore: remove authstore (#377)
  fix: handle duplicate connections to LocalPeers (#378)
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.

2 participants