Skip to content

chore(ci): retrigger Release after Rekor 409 - #207

Merged
pasevin merged 1 commit into
mainfrom
chore/retrigger-release-rekor
Aug 6, 2026
Merged

chore(ci): retrigger Release after Rekor 409#207
pasevin merged 1 commit into
mainfrom
chore/retrigger-release-rekor

Conversation

@pasevin

@pasevin pasevin commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Empty commit to get a new SHA so Release/publish.yml can run again after Rekor 409 blocked run 31094078486 on f2d90e3.
  • No workflow or package changes. Pending .changeset/write-completion-vocabulary.md should open the Version Packages PR once Release succeeds.

Test plan

  • Merge → Release workflow attempt 1 succeeds past provenance / slsa-setup
  • Version Packages PR appears for @openzeppelin/ui-types 3.5.0

Made with Cursor

Co-authored-by: Cursor <cursoragent@cursor.com>
@netlify

netlify Bot commented Aug 6, 2026

Copy link
Copy Markdown

Deploy Preview for openzeppelin-ui ready!

Name Link
🔨 Latest commit c10bf17
🔍 Latest deploy log https://app.netlify.com/projects/openzeppelin-ui/deploys/6a746cbb83180e0008743912
😎 Deploy Preview https://deploy-preview-207--openzeppelin-ui.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@pasevin
pasevin merged commit faaefbf into main Aug 6, 2026
14 checks passed
@pasevin
pasevin deleted the chore/retrigger-release-rekor branch August 6, 2026 11:19
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 6, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant