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

update: octocrab 0.24 -> 0.41 #5

Merged
merged 1 commit into from
Oct 31, 2024
Merged

update: octocrab 0.24 -> 0.41 #5

merged 1 commit into from
Oct 31, 2024

Conversation

0xB10C
Copy link
Owner

@0xB10C 0xB10C commented Oct 31, 2024

Next to keeping up-to-date with general GitHub API changes, this fixes #3.

Next to keeping up-to-date with general GitHub API changes, this
fixes fixes #3.
@0xB10C
Copy link
Owner Author

0xB10C commented Oct 31, 2024

I did a full backup of bitcoin-core/secp256k1 with this change (by deleting the state.json file locally) with cargo run -- --owner bitcoin-core --repo secp256k1 --destination /path/to/existing/backup --personal-access-token-file /path/to/token/file and the differences between old and new seem to be minimal.

There are now closed_by or merged_by fields that weren't there before and a new patch_url field has been added to users. Nothing that would hold me back from merging this.

@0xB10C 0xB10C merged commit 71a8124 into master Oct 31, 2024
1 check passed
@0xB10C 0xB10C deleted the 2024-10-update-octocrab branch October 31, 2024 13:22
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.

auto_squash_enabled event support missing
1 participant