Skip to content

Conversation

@ViacheslavKudinov
Copy link
Contributor

@ViacheslavKudinov ViacheslavKudinov commented Oct 29, 2025

Resolves #NaN


Before the change?

  • There is no artifacts attestation at this moment

After the change?

Pull request checklist

  • Schema migrations have been created if needed (example)
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes
  • No

@ViacheslavKudinov ViacheslavKudinov force-pushed the maintenance/add-attestation branch from 10dbe42 to cc98a12 Compare October 29, 2025 23:50
Signed-off-by: Viacheslav Kudinov <[email protected]>
@ViacheslavKudinov ViacheslavKudinov force-pushed the maintenance/add-attestation branch from cc98a12 to 4d2ad53 Compare October 29, 2025 23:50
@ViacheslavKudinov ViacheslavKudinov marked this pull request as ready for review October 29, 2025 23:52
@ViacheslavKudinov
Copy link
Contributor Author

ViacheslavKudinov commented Oct 30, 2025

Any known thing why we may regret by adding attestation?

Just loudly thinking if anything we need to consider

@ViacheslavKudinov ViacheslavKudinov changed the title chore(Actions): Add GH attestation on release process chore(actions): Add GH attestation on release process Nov 1, 2025
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.

1 participant