-
Notifications
You must be signed in to change notification settings - Fork 2
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
π (release) [DSDK-500]: Push snapshot release to jfrog #350
base: develop
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git βοΈ
|
4ee7572
to
5c8ebee
Compare
5c8ebee
to
4ef2077
Compare
4ef2077
to
817e2ea
Compare
if: steps.changesets.conclusion == 'success' | ||
uses: LedgerHQ/actions-security/actions/sign-blob@actions/sign-blob-1 | ||
with: | ||
path: ./dist |
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.
[ASK] should we do it before changeset ? as we push the artifact to jfrog there ?
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.
Yes we should, it's the only way to get access to the "builds" to attest and sign (it seems going through changeset publish, and subsequently pnpm publish, does not trigger the lifecycle of a normal publish, which leads to us not being able to hook into the lifecycle to get access to the "packed" libraries)
π Description
Update snapshot release to push to jfrog
β Context
β Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.
π§ Checklist for the PR Reviewers