Skip to content

Sync common files from infra repository#129

Merged
cgwalters merged 2 commits intomainfrom
sync-common-files
Mar 4, 2026
Merged

Sync common files from infra repository#129
cgwalters merged 2 commits intomainfrom
sync-common-files

Conversation

@bootc-bot
Copy link
Contributor

@bootc-bot bootc-bot bot commented Mar 3, 2026

Created by GitHub workflow (source).

This PR synchronizes common files from the infra repository.

Synchronized from bootc-dev/infra@eb09fd5.

@bootc-bot bootc-bot bot force-pushed the sync-common-files branch from f5acf96 to 8716824 Compare March 3, 2026 15:13
Synchronized from bootc-dev/infra@eb09fd5.

Signed-off-by: bootc-dev Bot <bot@bootc.dev>
@bootc-bot bootc-bot bot force-pushed the sync-common-files branch from 8716824 to 58da14c Compare March 3, 2026 19:23
Adding new fields to a publicly constructible struct is a semver
breaking change. Mark the struct as #[non_exhaustive] so that future
field additions are compatible, requiring users to use
`..Default::default()` when constructing the struct.

Fixes cargo-semver-checks failure from the insecure_policy field
addition.

Assisted-by: Claude Code (Opus 4.5)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Signed-off-by: Xiaofeng Wang <henrywangxf@me.com>
@henrywang
Copy link
Contributor

Hi @cgwalters , PR #127 added API break change. I think CI is right, adding #[non_exhaustive] now means future field additions won't be breaking.

@jeckersb
Copy link
Collaborator

jeckersb commented Mar 4, 2026

Hm #127 doesn't add #[non_exhausive] though, but it does add a new pub field to a pub struct which is a semver break. I'm not sure why the automation thinks it's been made non-exhaustive.

@jeckersb
Copy link
Collaborator

jeckersb commented Mar 4, 2026

Oh wait I see it's in this PR?? Wat.

@cgwalters
Copy link
Collaborator

Yes what happened is I merged #127 not noticing the semver check failed (because it's not gating) and @henrywang pushed an update to this PR on top of what renovate did - why did you do that instead of a separate PR?

@jeckersb
Copy link
Collaborator

jeckersb commented Mar 4, 2026

Ah ok I see it now, makes sense. I thought the sync action added that which thoroughly confused me.

@cgwalters cgwalters enabled auto-merge (squash) March 4, 2026 16:38
@cgwalters cgwalters merged commit c421628 into main Mar 4, 2026
3 of 4 checks passed
@henrywang henrywang deleted the sync-common-files branch March 5, 2026 08:54
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