Skip to content

[ripper37-libbase] Update port to v1.1.0 #45009

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

Conversation

RippeR37
Copy link
Contributor

  • Changes comply with the maintainer guide.
  • SHA512s are updated for each updated download.
  • The "supports" clause reflects platforms that may be fixed by this new version.
  • Any fixed CI baseline entries are removed from that file.
  • Any patches that are no longer applied are deleted from the port's directory.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Only one version is added to each modified port's versions file.

I'm not sure what is the proper way to note optionally-exposed targets for CMake in the usage file. Please let me know if I should modify it or if the current version is fine.

@Mengna-Li Mengna-Li added category:port-update The issue is with a library, which is requesting update new revision category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist labels Apr 14, 2025
@Mengna-Li Mengna-Li added the info:reviewed Pull Request changes follow basic guidelines label Apr 15, 2025
@BillyONeal BillyONeal closed this Apr 15, 2025
@BillyONeal BillyONeal reopened this Apr 15, 2025
@BillyONeal
Copy link
Member

Closed and reopened to trigger feature test.

@BillyONeal BillyONeal merged commit 0a0f5fc into microsoft:master Apr 16, 2025
19 checks passed
@BillyONeal
Copy link
Member

Thanks for the update!

@RippeR37 RippeR37 deleted the port/update/ripper37-libbase/v1.1.0 branch April 16, 2025 22:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist category:port-update The issue is with a library, which is requesting update new revision info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants