Skip to content
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

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

valpinkman
Copy link
Member

@valpinkman valpinkman commented Oct 3, 2024

πŸ“ Description

Update snapshot release to push to jfrog

⚠️ Draft for now as we need to understand how to pass the npm.distTag to jfrog when using snapshot releases

❓ Context

βœ… Checklist

Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

  • Covered by automatic tests.
  • Changeset is provided
  • Impact of the changes:
    • Push snapshot releases to jfrog

🧐 Checklist for the PR Reviewers

  • The code aligns with the requirements described in the linked JIRA or GitHub issue.
  • The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
  • There are no undocumented trade-offs, technical debt, or maintainability issues.
  • The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
  • Any new dependencies have been justified and documented.

Copy link

vercel bot commented Oct 3, 2024

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
device-sdk-ts-sample βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Oct 3, 2024 0:21am

Copy link
Contributor

github-actions bot commented Oct 3, 2024

Messages
⚠️ No changeset file found in the PR. Please add a changeset file.

Generated by 🚫 dangerJS against 817e2ea

@valpinkman valpinkman marked this pull request as draft October 3, 2024 12:12
if: steps.changesets.conclusion == 'success'
uses: LedgerHQ/actions-security/actions/sign-blob@actions/sign-blob-1
with:
path: ./dist
Copy link
Member

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 ?

Copy link
Member Author

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)

@valpinkman valpinkman added the hodl Do not merge label Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hodl Do not merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants