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

[Snyk] Upgrade @alaskaairux/design-tokens from 3.11.0 to 3.12.1 #140

Closed

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented Jan 7, 2023

Snyk has created this PR to upgrade @alaskaairux/design-tokens from 3.11.0 to 3.12.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released 24 days ago, on 2022-12-13.
Release notes
Package name: @alaskaairux/design-tokens from @alaskaairux/design-tokens GitHub release notes
Commit messages
Package name: @alaskaairux/design-tokens

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@snyk-bot snyk-bot requested a review from a team as a code owner January 7, 2023 07:23
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@blackfalcon blackfalcon deleted the snyk-upgrade-16d5f7be383a2581a1728e20eef89aee branch August 4, 2023 23:22
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.

3 participants