Skip to content

Add workspace-level lints for macro packages#4547

Open
heaths wants to merge 1 commit into
Azure:mainfrom
heaths:ignore-some-breaking-changes
Open

Add workspace-level lints for macro packages#4547
heaths wants to merge 1 commit into
Azure:mainfrom
heaths:ignore-some-breaking-changes

Conversation

@heaths

@heaths heaths commented Jun 6, 2026

Copy link
Copy Markdown
Member

Introduce workspace-level lint configurations across multiple Cargo.toml files
to ensure public model structs remain constructible when fields are added.
This encourages downstream code to utilize ..Default::default() for new optional
fields, preventing breaking changes in initializers.

Introduce workspace-level lint configurations across multiple Cargo.toml files
to ensure public model structs remain constructible when fields are added.
This encourages downstream code to utilize `..Default::default()` for new optional
fields, preventing breaking changes in initializers.
Copilot AI review requested due to automatic review settings June 6, 2026 01:26
@heaths heaths removed the request for review from Copilot June 6, 2026 01:26
@github-actions github-actions Bot added Azure.Core The azure_core crate Event Hubs Storage Storage Service (Queues, Blobs, Files) labels Jun 6, 2026
rohitsinghal4u pushed a commit that referenced this pull request Jun 7, 2026
…lint exemption

Cherry-picked PR #4547 adds 'constructible_struct_adds_field = allow' at the workspace level, so we no longer need a major-version bump when the regen adds optional fields to existing non-non_exhaustive model structs (CertificatePolicy, KeyAttributes, DeletedKeyProperties). Revert both crates back to 1.1.0-beta.1 and update changelogs to drop the Breaking Changes note.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure.Core The azure_core crate Event Hubs Storage Storage Service (Queues, Blobs, Files)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant