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

libgit2 1.9.0 #202651

Merged
merged 68 commits into from
Jan 2, 2025
Merged

libgit2 1.9.0 #202651

merged 68 commits into from
Jan 2, 2025

Conversation

BrewTestBot
Copy link
Member

Created by brew bump


Created with brew bump-formula-pr.

release notes
This is release v1.9.0, "Schwibbogen". As usual, it contains numerous bug fixes, compatibility improvements, and new features.

This is expected to be the final release in the libgit2 v1.x lineage. libgit2 v2.0 is expected to be the next version, with support for SHA256 moving to "supported" status (out of "experimental" status). This means that v2.0 will have API and ABI changes to support SHA256, as well as other breaking changes.

Major changes

  • Documentation improvements
    We've launched a new website for our API reference docs at https://libgit2.org/docs/reference/main. To support this, we've updated the documentation to ensure that all APIs are well-documented, and added docurium-style specifiers to indicate more depth about the API surface.

    We now also publish a JSON blob with the API structure and the documentation that may be helpful for binding authors.

  • TLS cipher updates
    libgit2 has updated our TLS cipher selection to match the "compatibility" cipher suite settings as documented by Mozilla.

  • Blame improvements
    The blame API now contains committer information and commit summaries for blame hunks, and the ability to get information about the line of text that was modified. In addition, a CLI blame command has been added so that the blame functionality can be benchmarked by our benchmark suite.

  • More CLI commands
    libgit2 has added blame and init commands, which have allowed for further benchmarking and several API improvements and git compatibility updates.

  • Warning when configuring without SHA1DC
    Users are encouraged to use SHA1DC, which is git's hash; users should not use SHA1 in the general case. Users will now be warned if they try to configure cmake with a SHA1 backend (-DUSE_SHA1=...).

Breaking changes

There are several ABI-breaking changes that integrators, particularly maintainers of bindings or FFI users, may want to be aware of.

  • Blame hunk structure updates (ABI breaking change)
    There are numerous additions to the git_blame_hunk structure to accommodate more information about the blame process.

  • Checkout strategy updates (ABI breaking change)
    The values for GIT_CHECKOUT_SAFE and GIT_CHECKOUT_NONE have been updated. GIT_CHECKOUT_SAFE is now 0; this was implicitly the default value (with the options constructors setting that as the checkout strategy). It is now the default if the checkout strategy is set to 0. This allows for an overall code simplification in the library.

  • Configuration entry member removal (ABI breaking change)
    The git_config_entry structure no longer contains a free member; this was an oversight as end-users should not try to free that structure.

  • Configuration backend function changes (ABI breaking change)
    git_config_backends should now return git_config_backend_entry objects instead of git_config_entry objects. This allows backends to provide a mechanism to nicely free the configuration entries that they provide.

What's Changed

New features

Bug fixes

Security fixes

Code cleanups

Benchmarks

Build and CI improvements

Documentation improvements

Git compatibility fixes

Dependency updates

Other changes

New Contributors

Full Changelog: libgit2/libgit2@v1.8.4...v1.9.0

@github-actions github-actions bot added the bump-formula-pr PR was created using `brew bump-formula-pr` label Dec 28, 2024
@carlocab
Copy link
Member

Should be able to skip revision bumps for literate-git and dvc after #202657 and #202656.

But pygit2 will likely need a [email protected].

Copy link
Contributor

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a help wanted or in progress label.

@github-actions github-actions bot added the stale No recent activity label Dec 31, 2024
@carlocab carlocab removed the stale No recent activity label Dec 31, 2024
@chenrui333 chenrui333 added the in progress Stale bot should stay away label Dec 31, 2024
@chenrui333
Copy link
Member

chenrui333 commented Jan 1, 2025

libgit2-sys needs to be updated to use libgit2 1.9, rust-lang/git2-rs#1109 (it would affect all the rust formulae)


for pygit2, waiting this to be released

@github-actions github-actions bot added automerge-skip `brew pr-automerge` will skip this pull request new formula PR adds a new formula to Homebrew/homebrew-core labels Jan 1, 2025
@chenrui333 chenrui333 added long build Set a long timeout for formula testing CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. labels Jan 1, 2025
@carlocab carlocab force-pushed the bump-libgit2-1.9.0 branch from f1f82cd to c908009 Compare January 1, 2025 16:16
@carlocab carlocab removed the automerge-skip `brew pr-automerge` will skip this pull request label Jan 1, 2025
@carlocab carlocab force-pushed the bump-libgit2-1.9.0 branch from c908009 to fe1564c Compare January 1, 2025 16:36
@github-actions github-actions bot added the automerge-skip `brew pr-automerge` will skip this pull request label Jan 1, 2025
@carlocab carlocab removed the automerge-skip `brew pr-automerge` will skip this pull request label Jan 1, 2025
@cho-m cho-m added 13 Ventura is specifically affected 13-arm64 Ventura arm64 is specifically affected labels Jan 2, 2025
@carlocab carlocab force-pushed the bump-libgit2-1.9.0 branch from fe1564c to b95e3cc Compare January 2, 2025 05:01
@carlocab carlocab added ready to merge PR can be merged once CI is green no long build conflict Do not allow merging other pull requests when files conflict with this one labels Jan 2, 2025
@github-actions github-actions bot added the automerge-skip `brew pr-automerge` will skip this pull request label Jan 2, 2025
@carlocab carlocab removed the automerge-skip `brew pr-automerge` will skip this pull request label Jan 2, 2025
@carlocab carlocab force-pushed the bump-libgit2-1.9.0 branch from b95e3cc to 196dc50 Compare January 2, 2025 07:46
@github-actions github-actions bot added the automerge-skip `brew pr-automerge` will skip this pull request label Jan 2, 2025
@github-actions github-actions bot added the CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. label Jan 2, 2025
@BrewTestBot BrewTestBot enabled auto-merge January 2, 2025 19:13
@BrewTestBot BrewTestBot added this pull request to the merge queue Jan 2, 2025
Merged via the queue into master with commit 80df43a Jan 2, 2025
15 checks passed
@BrewTestBot BrewTestBot deleted the bump-libgit2-1.9.0 branch January 2, 2025 19:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bump-formula-pr PR was created using `brew bump-formula-pr` CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. in progress Stale bot should stay away long build Set a long timeout for formula testing new formula PR adds a new formula to Homebrew/homebrew-core no long build conflict Do not allow merging other pull requests when files conflict with this one ready to merge PR can be merged once CI is green
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants