Skip to content

Conversation

@ArtificialOwl
Copy link
Member

  • moving Security/Signature from unstable to public
  • setting previous code from unstable as deprecated

@ArtificialOwl ArtificialOwl requested review from a team and nickvergessen as code owners September 3, 2025 11:17
@ArtificialOwl ArtificialOwl requested review from CarlSchwan, icewind1991 and leftybournes and removed request for a team September 3, 2025 11:17
@ArtificialOwl ArtificialOwl marked this pull request as draft September 3, 2025 12:37
@ArtificialOwl ArtificialOwl force-pushed the feat/noid/move-sec-signature-to-public branch 2 times, most recently from 3d9ebf9 to cf2a86d Compare September 3, 2025 14:04
@nickvergessen
Copy link
Member

🛑 Feature freeze was like 4 Weeks ago. We are less than 24h away from RC1. From my POV this is not the correct time to flip over an API like this.
My take: Do it after Thursday on master only for 33.

@nickvergessen
Copy link
Member

Time to rebase and update the version numbers to 33 and then get it in?

@ArtificialOwl ArtificialOwl force-pushed the feat/noid/move-sec-signature-to-public branch from cf2a86d to c2b6b43 Compare January 7, 2026 12:40
@ArtificialOwl ArtificialOwl force-pushed the feat/noid/move-sec-signature-to-public branch from c2b6b43 to e17c569 Compare January 7, 2026 13:25
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