Skip to content

chore(vcpkg): bump default baseline hash of vcpkg#6870

Merged
waruqi merged 1 commit intoxmake-io:devfrom
yingmanwumen:dev
Sep 29, 2025
Merged

chore(vcpkg): bump default baseline hash of vcpkg#6870
waruqi merged 1 commit intoxmake-io:devfrom
yingmanwumen:dev

Conversation

@yingmanwumen
Copy link
Contributor

Update the default vcpkg baseline to a more recent commit (2025.09.27) to ensure xmake uses up-to-date vcpkg ports.

  • Before adding new features and new modules, please go to issues to submit the relevant feature description first.
  • Write good commit messages and use the same coding conventions as the rest of the project.
  • Please commit code to dev branch and we will merge into master branch in feature
  • Ensure your edited codes with four spaces instead of TAB.

  • 增加新特性和新模块之前,请先到issues提交相关特性说明,经过讨论评估确认后,再进行相应的代码提交,避免做无用工作。
  • 编写友好可读的提交信息,并使用与工程代码相同的代码规范,代码请用4个空格字符代替tab缩进。
  • 请提交代码到dev分支,如果通过,我们会在特定时间合并到master分支上。
  • 为了规范化提交日志的格式,commit消息,不要用中文,请用英文描述。

Update the default vcpkg baseline to a more recent commit (2025.09.27)
to ensure xmake uses up-to-date vcpkg ports.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @yingmanwumen, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the internal reference for the vcpkg package manager within xmake. By bumping the default baseline hash to a more recent commit, xmake will now leverage a newer set of vcpkg ports, ensuring access to updated dependencies and potentially improved compatibility or features for projects using vcpkg through xmake.

Highlights

  • Vcpkg Baseline Update: The default vcpkg baseline hash has been updated from "44d94c2edbd44f0c01d66c2ad95eb6982a9a61bc" (2021.04.30) to "2e6fcc44573d091af0321f99c89b212997a76f1f" (2025.09.27). This ensures that xmake utilizes more current vcpkg ports.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the default vcpkg baseline hash, which is a good maintenance task. My review includes one suggestion to correct a likely typo in the date associated with the new commit hash in the code comment. This will help maintain the accuracy of the code's documentation and prevent confusion. Please note that the same typo appears in the pull request description.


-- generate manifest, vcpkg.json
local baseline = configs.baseline or "44d94c2edbd44f0c01d66c2ad95eb6982a9a61bc" -- 2021.04.30
local baseline = configs.baseline or "2e6fcc44573d091af0321f99c89b212997a76f1f" -- 2025.09.27
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The date in the comment, 2025.09.27, appears to have a typo in the year. A git commit is a historical record and cannot have a date from the future. The correct year for this commit hash is likely 2023. Updating the comment to be accurate will improve clarity and prevent confusion for other developers.

    local baseline = configs.baseline or "2e6fcc44573d091af0321f99c89b212997a76f1f" -- 2023.09.27

@waruqi waruqi merged commit 87451e3 into xmake-io:dev Sep 29, 2025
21 of 22 checks passed
@waruqi waruqi added this to the v3.0.4 milestone Sep 29, 2025
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