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

Version Packages #294

Conversation

ldg-github-ci
Copy link

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to feat/no-issue-jfrog-attest-sign-package, this PR will be updated.

Releases

@ledgerhq/[email protected]

Minor Changes

Patch Changes

@ledgerhq/[email protected]

Minor Changes

Patch Changes

@ledgerhq/[email protected]

Minor Changes

Patch Changes

@ledgerhq/[email protected]

Patch Changes

@ledgerhq/[email protected]

Patch Changes

@github-actions github-actions bot force-pushed the changeset-release/feat/no-issue-jfrog-attest-sign-package branch from f7d314c to 7acaf87 Compare September 19, 2024 16:16
Copy link

vercel bot commented Sep 19, 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 Sep 19, 2024 4:49pm

Copy link
Contributor

Fails
🚫

Please fix the PR branch name to match the convention, see this documentation.

Wrong branch name: changeset-release/feat/no-issue-jfrog-attest-sign-package

ℹ️ Regex to match: /^(feature|feat|bugfix|bug|hotfix|fix|support|chore|core|doc|refacto|refactor)\/((dsdk)-[0-9]+|no-issue)-.+/i

  • Rules:
    • Must start with a type (feature, bugfix, hotfix, support, chore, core, doc, refacto)
    • Followed by a SLASH ("/")
    • Followed by a JIRA issue number (DSDK-1234) or "no-issue"
    • Followed by a DASH ("-")
    • Followed by a description

ℹ️ Example: feat/dsdk-1234-my-feature

🚫

One or more commit message does not match the convention, see this documentation.

Wrong commit messages:
Merge 006b227b4bb011b5b38cbc02a7dded5aa5bbfbc0 into f03c328e98c79f8b2a8f71004e87eae8f56bb481
Version Packages

ℹ️ Regex to match: /^.+\(([a-z]+\-?){1,}\): [A-Z].*/

  • Rules:
    • Must start with a word (usually an emoji)
    • Followed by a SPACE
    • Followed by a scope in parentheses and in LOWERCASE
    • Followed by a colon (":") and a SPACE
    • Followed by a Capitalized message

Example: 💚 (scope): My feature

🚫

Please fix the PR title to match the convention, see this documentation.

Wrong PR title: Version Packages

ℹ️ Regex to match: /^.+ \(([a-z]+\-?){1,}\) \[(DSDK-[0-9]+|NO-ISSUE)\]: [A-Z].*/

  • Rules:
    • Must start with a word (usually an emoji)
    • Followed by a SPACE
    • Followed by a scope in parentheses and in LOWERCASE
    • Followed by a SPACE
    • Followed by a JIRA issue number in [brackets] (uppercase)
    • Followed by a colon (":") and a SPACE
    • Followed by a Capitalized message

Example: 💚 (scope) [DSDK-1234]: My feature

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

Generated by 🚫 dangerJS against 7acaf87

@github-actions github-actions bot force-pushed the changeset-release/feat/no-issue-jfrog-attest-sign-package branch from 7acaf87 to 753549f Compare September 19, 2024 16:47
@dedsxc dedsxc closed this Sep 19, 2024
@dedsxc dedsxc deleted the changeset-release/feat/no-issue-jfrog-attest-sign-package branch September 19, 2024 16:53
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.

2 participants