-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(@lexical/devtools): Publish pipeline added #5924
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
c38bb93
to
0065b34
Compare
size-limit report 📦
|
|
||
jobs: | ||
release: | ||
if: github.repository_owner == 'facebook' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's the purpose of this condition?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks right - I expected a checksum or signing step of some sort, though?
So signing happens at the store side after version review. We simply upload zip there and they do review + signing. |
This adds publish pipeline draft (as I'm still waiting for stores approval for FF/Edge + license update for Apple/Chrome).
All secrets were added to repo and I'll publish access request procedure in the follow up diff that adds Chrome/Safari