Skip to content

(PA-8304): Add osx-26-x86_64 to foss_platforms in builder_data.yaml#265

Open
span786 wants to merge 1 commit intoreleasefrom
PA-8304-10-update-builder-data-yaml-to-enable-macos-26-intel-for-public-nightlies-ship
Open

(PA-8304): Add osx-26-x86_64 to foss_platforms in builder_data.yaml#265
span786 wants to merge 1 commit intoreleasefrom
PA-8304-10-update-builder-data-yaml-to-enable-macos-26-intel-for-public-nightlies-ship

Conversation

@span786
Copy link
Copy Markdown
Contributor

@span786 span786 commented Apr 2, 2026

Add osx-26-x86_64 to foss_platforms in builder_data.yaml

Note: Due to a bug (PR puppet-private #130) affecting macOS 26 on Intel, we do not want to proceed with Puppet 9 nightly releases for this platform. However, Puppet 8.x is good to go for macOS 26 Intel.

@span786 span786 requested a review from a team as a code owner April 2, 2026 10:20
- osx-14-arm64
- osx-15-x86_64
- osx-15-arm64
- osx-26-x86_64
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Will this break puppet 9 when we try to ship it? I suppose we have the same issue now. el-6-x86_64 is listed here, but we don't build/ship it in puppet 8. What does this repo do with foss_platforms and why isn't it pulled from the repo that produced the artifact https://github.com/puppetlabs/puppet-agent-private/blob/8.x/ext/build_defaults.yaml#L12 (so the list of packages to ship is versioned with the code)?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm not sure what all is controlled by it, but I know that it overrides what is in the build_defaults in some packaging code. There was a fairly recent discussion about it here: https://perforce.slack.com/archives/C04J7N6R761/p1771416311613629

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.

3 participants