Skip to content

[Snyk] Upgrade @formkit/themes from 1.3.0 to 1.5.2#571

Closed
riderx wants to merge 1 commit intomainfrom
snyk-upgrade-87a4f7197be09b4fb29d7a6d959d767b
Closed

[Snyk] Upgrade @formkit/themes from 1.3.0 to 1.5.2#571
riderx wants to merge 1 commit intomainfrom
snyk-upgrade-87a4f7197be09b4fb29d7a6d959d767b

Conversation

@riderx
Copy link
Copy Markdown
Member

@riderx riderx commented Feb 16, 2024

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade @formkit/themes from 1.3.0 to 1.5.2.

ℹ️ 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 29 versions ahead of your current version.
  • The recommended version was released 23 days ago, on 2024-01-23.
Release notes
Package name: @formkit/themes
  • 1.5.2 - 2024-01-23
  • 1.5.1 - 2024-01-19

    🐛 Bug fixes

    • Fixes a bug introduced in 1.5.0 that caused the context.value to not properly synced with the node.value inside of nested group structures (#1133).
  • 1.5.0 - 2024-01-16

    FormKit 1.5.0 ships with a new development build of FormKit. In development FormKit now uses slightly different versions of its packages that include additional developer experience enhancements. This is similar to how Vue itself has "development" and "production" versions, and it allows FormKit to provide an improved developer experience such as improved HMR support and better error messages.

    The groundwork is now laid for greatly improved developer experience in future releases. This release also includes dozens of bug fixes and improvements.

    💪 New features

    • Adds a new API for adding props to inputs with default values, boolean props, and getters/setters. See the updated docs for more info.
    • createInput now supports a third argument, sectionsSchema which allows you to extend the default sections that come with createInput (#882).
    • Adds new context property didMount and node event mounted to recognize when the <FormKit> component is mounted to the DOM (#0b8753d).
    • Now node.children are observed by @ formkit/observer, this allows validation rules to access node.children with reactivity.
    • Hot module replacement with Vite/Nuxt now preserve the form state when updating form code (#1068)
    • Adds new changeLocale composable that globally changes the locale of all forms with Options API, Composition API, and Nuxt autoimport (#1112)
    • Rules allow_non_alpha and allow_numeric.
    • The new FormKit cli now scaffolds new apps (npx formkit create-app) to use themes.formkit.com’s theme system.
    • New development build of FormKit that includes additional developer experience enhancements.

    🐛 Bug fixes

    • Fixes Vite TSDoc comment warnings - by Yue Yang (e47c9)
    • Fix windows create-app name for nuxt projects (1066)
    • Inputs that use options (select, checkbox, radio, autocomplete etc) now properly count their __mask value (#1046).
    • Fixes a bug that did now allow submitAttrs to disable submit input (#789).
    • Removes data-disabled on checkbox and radio inputs when false - (#1043).
    • Fixes autoAnimate when used on repeaters and other inputs with complex conditionals (#1016).
    • Significantly improves @ formkit/nuxt’s experimental autoImport feature (1095, and others).
    • Autoheight textarea hydration in nuxt (#980).
    • Adds non-blocking messages in getValidationMessages (#849).
    • node.clearErrors() always removes errors local to that node (#941)
    • Reduces re-renders on destructured group values (#1068).
    • Removes warning on multi-step about default slot being called outside render function (#920).
    • Inputs inside a disabled repeater can be enabled per-input (#1043).
    • Improves typing for createInput() (#1105).
    • Removes data-complete on groups/lists (#1038).
    • Boolean props like disabled and preserve can now be used without explicitly setting them to true or false (#989).

    Important

    Vitest does not automatically use the same node parameters (conditions) that Vite does (see #4971). If you find your tests failing after you update, you can add the following to your vitest.config.js file:

  • 1.5.0-fd1b1b4 - 2024-01-10
  • 1.5.0-e8f4df1 - 2024-01-10
  • 1.5.0-e10ee61 - 2023-12-30
  • 1.5.0-bfd1e74 - 2024-01-04
  • 1.5.0-b35d51f - 2023-12-29
  • 1.5.0-a744393 - 2024-01-12
  • 1.5.0-81c16e6 - 2023-12-21
  • 1.5.0-6c909ab - 2023-12-05
  • 1.5.0-6a47acc - 2024-01-02
  • 1.5.0-5d72fc3 - 2024-01-02
  • 1.5.0-54a1993 - 2023-12-21
  • 1.5.0-4c8ec61 - 2024-01-02
  • 1.5.0-2087d2b - 2023-12-28
  • 1.5.0-180b85c - 2024-01-12
  • 1.5.0-11da1c5 - 2024-01-02
  • 1.5.0-09bb95c - 2024-01-15
  • 1.5.0-081ab91 - 2024-01-11
  • 1.5.0-7533531 - 2023-12-22
  • 1.5.0-3001515 - 2024-01-10
  • 1.4.0 - 2023-12-05

    💪 New features

    • FormKit now supports themes for TailwindCSS! Customize the look and feel of your forms with a visual editor. See themes.formkit.com for more information.
    • Adds new <KitchenSink> component that renders a specimen of every FormKit input (helpful for styling).
    • Adds new state.required property to the context object (makes adding asterisks to required inputs easier).
    • Adds aria-required attribute to <input>, <select>, and <textarea> elements when they are required (#984).
    • Adds new force-show prop to the <FormKitSummary> component to force the summary to show even if there are no visible errors.
    • Adds new create-theme command for the formkit CLI tool to scaffold a new theme from @ formkit/theme-starter.

    🐛 Bug fixes

    • Fixes a bug that caused radio inputs inside repeaters to become coupled (#1044).
    • Fixed an issue that caused node.submit() to fail when inside a custom element’s shadow root (#1057).
    • Fixes a bug that caused pro inputs to not produce proper memokeys (#933).
    • Fixed a bug that caused attributes to not pass through <FormKitProvider> (and related providers) (#1013).
    • Moved the invalidDate message to the to the validation locale key (#953)
    • Improved the min and max validation message (en) to be the validation locale key (#953)
    • Fixed a bug that prevented the incomplete-message prop (on forms) from being reactive (#1047).
  • 1.4.0-c54b8c0 - 2023-11-16
  • 1.4.0-3250d9b - 2023-12-05
  • 1.4.0-2c9b645 - 2023-12-05
  • 1.4.0-1ecfde2 - 2023-12-05
  • 1.3.2 - 2023-11-28
  • 1.3.1 - 2023-11-28
  • 1.3.0 - 2023-11-09
from @formkit/themes GitHub release notes

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

@netlify
Copy link
Copy Markdown

netlify Bot commented Feb 16, 2024

Deploy Preview for webcapgo failed.

Name Link
🔨 Latest commit e8adac0
🔍 Latest deploy log https://app.netlify.com/sites/webcapgo/deploys/65ceb9a1bccff800074033fd

@sonarqubecloud
Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@socket-security
Copy link
Copy Markdown

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@formkit/themes@1.5.2 network Transitive: environment, eval, filesystem, shell, unsafe +121 56.2 MB justin-schroeder

View full report↗︎

@riderx riderx closed this Feb 18, 2024
@riderx riderx deleted the snyk-upgrade-87a4f7197be09b4fb29d7a6d959d767b branch October 30, 2024 07:29
riderx pushed a commit that referenced this pull request Apr 29, 2026
* feat(cli): migrate CLI auth checks to RBAC-aware permissions

Port CLI PR #571 (Cap-go/CLI) changes into monorepo cli/ workspace.

Migrates all CLI auth checks to RBAC-aware backend wrappers
(hasCliPermission, filterOrgsByPermission, getOrganizationListWithPermission,
resolveUserIdFromApiKey). Makes login, user account, and organization add
identity-only (no legacy key-mode gating). Uses org.create_app permission
key for app creation and init flow. Legacy fallback semantics preserved
for older API keys.

Includes build/request.ts refactoring to reduce cognitive complexity and
extract helpers (dispatchCustomMsg, WsEntry interface).

* fix(cli): remove unused getInstalledVersion import in init/command.ts

* fix(cli): remove redundant resolveUserIdFromApiKey calls in build and compatibility

assertCliPermission and checkAppExistsAndHasPermissionOrgErr already
validate API key permissions independently via cli_check_permission RPC.
The prior identity gate was redundant and could incorrectly reject
scoped or service keys that have valid permissions but don't resolve
to a user.

* fix(cli): clear all restored globals when discarding resumed onboarding state

discardResumedState() now resets all globals that tryResumeOnboarding()
may have restored (globalAppId, globalPathToPackageJson, globalChannelName,
globalPlatform, globalDelta, globalCurrentVersion, globalOrgId,
globalOrgName) and sets resumed to undefined. This prevents stale values
from a previous onboarding session leaking into the fresh org flow.

* fix(cli): resolve TS18048 'resumed' possibly undefined after let reassignment

Capture resumed into a const resumedSnapshot at the top of the if-block
so TypeScript can narrow the type correctly across await boundaries.
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