miles/macosx-sdks
1
0
Fork 0
Code Issues 1 Pull requests Releases 26 Activity

feat: MacOSX26.0.sdk.tar.xz #9

Merged
socheatsok78 merged 1 commit from MacOSX26.0 into master 2025-10-23 14:37:02 -05:00
Conversation 6 Commits 1 Files changed 2 +14
socheatsok78 commented 2025-10-09 02:55:48 -05:00 (Migrated from github.com)
Copy link

Add MacOSX26.0.sdk.tar.xz

Add `MacOSX26.0.sdk.tar.xz` - Download: https://github.com/socheatsok78/macos-sdks/releases/download/rolling/MacOSX26.0.sdk.tar.xz - SHA256SUM: `07ccaa2891454713c3a230dd87283f76124193309d9a7617ebee45354c9302d2`
joseluisq (Migrated from github.com) approved these changes 2025-10-22 02:07:56 -05:00
joseluisq (Migrated from github.com) left a comment
Copy link

It looks fine to me.

Btw, I like your CI approach; we could integrate it into the project as well. Let me know.

Also, feel free to add the next macos 26.1.

It looks fine to me. Btw, I like your CI approach; we could integrate it into the project as well. Let me know. Also, feel free to add the next `macos 26.1`.
socheatsok78 commented 2025-10-22 03:25:51 -05:00 (Migrated from github.com)
Copy link

Btw, I like your CI approach; we could integrate it into the project as well. Let me know.

Thank you, I'm still testing the idea. Will open another PR in the future if it works as expected.

Also, feel free to add the next macos 26.1.

Yes, i'm still waiting the release from Apple and GitHub.

> Btw, I like your CI approach; we could integrate it into the project as well. Let me know. Thank you, I'm still testing the idea. Will open another PR in the future if it works as expected. > Also, feel free to add the next `macos 26.1`. Yes, i'm still waiting the release from Apple and [GitHub](https://github.com/actions/runner-images).
joseluisq commented 2025-10-23 02:02:20 -05:00 (Migrated from github.com)
Copy link

Thank you, I'm still testing the idea. Will open another PR in the future if it works as expected.

In fact, checksum generation should also be part of it.

Yes, i'm still waiting the release from Apple and GitHub.

What do you mean by that? The MacOSX26.1.sdk.tar.xz you already have it on the release.

> Thank you, I'm still testing the idea. Will open another PR in the future if it works as expected. In fact, checksum generation should also be part of it. > Yes, i'm still waiting the release from Apple and [GitHub](https://github.com/actions/runner-images). What do you mean by that? The `MacOSX26.1.sdk.tar.xz` you already have it on the release.
socheatsok78 commented 2025-10-23 03:02:49 -05:00 (Migrated from github.com)
Copy link

In fact, checksum generation should also be part of it.

Do you think we can trust the checksum generate automatically by GitHub, since each artifact uploaded to the release, GitHub will automatically generate the sha256 for each files. It not difficult to add checksum to the workflow but I reckon it already exists in the release xD

The MacOSX26.1.sdk.tar.xz you already have it on the release

About that, It was generated using a beta version of Xcode that came pre-install in the macos-26 runner image. So I think that I'll should wait for the stable release of Xcode and macOS 26.1 first before adding it.

I can add a filter to avoid generating SDK from beta version of Xcode, but I was in a rush and i just take whatever it gives me at that time, hehe

See https://github.com/actions/runner-images/blob/main/images/macos/macos-26-arm64-Readme.md#xcode

> In fact, checksum generation should also be part of it. Do you think we can trust the checksum generate automatically by GitHub, since each artifact uploaded to the release, GitHub will automatically generate the sha256 for each files. It not difficult to add checksum to the workflow but I reckon it already exists in the release xD > The `MacOSX26.1.sdk.tar.xz` you already have it on the release About that, It was generated using a `beta` version of Xcode that came pre-install in the `macos-26` runner image. So I think that I'll should wait for the stable release of Xcode and macOS 26.1 first before adding it. I can add a filter to avoid generating SDK from `beta` version of Xcode, but I was in a rush and i just take whatever it gives me at that time, hehe See https://github.com/actions/runner-images/blob/main/images/macos/macos-26-arm64-Readme.md#xcode
joseluisq commented 2025-10-23 03:23:22 -05:00 (Migrated from github.com)
Copy link

Do you think we can trust the checksum generate automatically by GitHub, since each artifact uploaded to the release, GitHub will automatically generate the sha256 for each files. It not difficult to add checksum to the workflow but I recok it already exists in the release xD

Yes, there is a built-in checksum per artifact in the GitHub release, which is fine. But what I meant is that this project provides a checksum file (sha256sum.txt), so this text file should also be uploaded per SDK.

About that, It was generated using a beta version of Xcode that came pre-install in the macos-26 runner image. So I think that I'll should wait for the stable release of Xcode and macOS 26.1 first before adding it. See https://github.com/actions/runner-images/blob/main/images/macos/macos-26-arm64-Readme.md#xcode

I understand, I didn't read that part. Make sense wait for it. However, if CI is integrated, it should make sure to use a stable Xcode.

> Do you think we can trust the checksum generate automatically by GitHub, since each artifact uploaded to the release, GitHub will automatically generate the sha256 for each files. It not difficult to add checksum to the workflow but I recok it already exists in the release xD Yes, there is a built-in checksum per artifact in the GitHub release, which is fine. But what I meant is that this project provides a checksum file (`sha256sum.txt`), so this text file should also be uploaded per SDK. > About that, It was generated using a `beta` version of Xcode that came pre-install in the `macos-26` runner image. So I think that I'll should wait for the stable release of Xcode and macOS 26.1 first before adding it. See https://github.com/actions/runner-images/blob/main/images/macos/macos-26-arm64-Readme.md#xcode I understand, I didn't read that part. Make sense wait for it. However, if CI is integrated, it should make sure to use a stable Xcode.
socheatsok78 commented 2025-10-23 03:28:31 -05:00 (Migrated from github.com)
Copy link

Ah yeah sorry, I'll note this down and will open another PR integrating the workflow to this repo. Need to make a few changes first xD

Ah yeah sorry, I'll note this down and will open another PR integrating the workflow to this repo. Need to make a few changes first xD
👍 1
Sign in to join this conversation.
Reviewers
No reviewers
joseluisq
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
miles/macosx-sdks!9
No description provided.