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

feat!: update @ucanto/interface dependencies #310

Merged
merged 1 commit into from
May 22, 2023
Merged

feat!: update @ucanto/interface dependencies #310

merged 1 commit into from
May 22, 2023

Conversation

travis
Copy link
Member

@travis travis commented May 22, 2023

@ucanto/interface had breaking changes, but because code in dependant libraries didn't change, release-please didn't cut new releases.

by manually specifying that the @ucanto/interface dependency must by 8 or above, this should trigger a release-please flow to release @ucanto/interface@8-compatible releases of these four libs.

`@ucanto/interface` had breaking changes, but because code in dependant libraries didn't change, release-please didn't cut new releases.

by manually specifying that the `@ucanto/interface` dependency must by 8 or above, this should trigger a release-please flow to release `@ucanto/interface@8`-compatible releases of these four libs.
@travis travis requested a review from Gozala May 22, 2023 19:51
Copy link
Collaborator

@Gozala Gozala 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 to me. I don't think principal got affected and needs bump but it's fine either way. I think we probably want to revert this after things get released.

@@ -29,7 +29,7 @@
"dependencies": {
"@ipld/dag-ucan": "^3.3.2",
"@noble/ed25519": "^1.7.3",
"@ucanto/interface": "workspace:^",
"@ucanto/interface": "workspace:^8",
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't think anything here was affected so not sure we need to force update

Copy link
Member Author

Choose a reason for hiding this comment

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

I think you're right - I'm going to just go ahead and release it to make the upgrade a little easier for downstream folks (ie, "update everything to 8" rather than "update almost everything to 8")

@travis travis merged commit 3d1adbf into main May 22, 2023
@github-actions github-actions bot mentioned this pull request May 22, 2023
@travis
Copy link
Member Author

travis commented May 22, 2023

I think we probably want to revert this after things get released.

I think that's correct - will follow up with a chore PR once this is released

travis added a commit that referenced this pull request May 22, 2023
Gozala pushed a commit that referenced this pull request Jul 13, 2023
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