-
Notifications
You must be signed in to change notification settings - Fork 28
chore: update @cowprotocol/permit-utils
#943
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Verify integration of the new RC release
You’ve upgraded
@cowprotocol/permit-utilsto^0.7.0-RC.0. Please ensure that:yarn.lockorpackage-lock.json) has been updated and committed alongside this bump.Run this script to confirm lockfile updates and locate all import sites for manual review:
🏁 Script executed:
Length of output: 258
Action Required: Commit Updated Lockfile & Verify API Usage
The RC bump for
@cowprotocol/permit-utilswas applied in package.json but no lockfile changes were detected. Please address the following before merging:• package.json (line 44): You’ve upgraded to
^0.7.0-RC.0.– Review the library’s CHANGELOG or migration guide for any breaking changes.
• Lockfile: Run
npm installoryarn installand commit the resultingpackage-lock.jsonoryarn.lock.• Import sites & API calls: Locate all references and confirm compatibility by running:
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one of the files of this PR is literally
yarn.lock!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 453
🏁 Script executed:
Length of output: 239
🏁 Script executed:
Length of output: 543
@cowdan You're absolutely right, and I apologize for the error! 🤦♀️
I can now see that
yarn.lockis indeed present and contains the updated@cowprotocol/permit-utils@^0.7.0-RC.0entry:My initial script failed to detect the changes properly. Thank you for the correction! The lockfile has been properly updated alongside the package.json change, so that aspect of the upgrade is handled correctly.
The only remaining consideration would be to verify that any breaking changes in the RC version are compatible with your existing code, but the dependency management side is properly taken care of.