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

fix(deps): update all non-major dependencies #178

Merged
merged 1 commit into from
Sep 30, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 30, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@solidjs/router 0.14.5 -> 0.14.7 age adoption passing confidence dependencies patch
@solidjs/testing-library 0.8.9 -> 0.8.10 age adoption passing confidence devDependencies patch
@types/lodash (source) 4.17.7 -> 4.17.9 age adoption passing confidence devDependencies patch
@typescript-eslint/eslint-plugin (source) 8.6.0 -> 8.7.0 age adoption passing confidence devDependencies minor
@typescript-eslint/parser (source) 8.6.0 -> 8.7.0 age adoption passing confidence devDependencies minor
JamesIves/github-pages-deploy-action v4.6.4 -> v4.6.8 age adoption passing confidence action patch
prettier-plugin-tailwindcss 0.6.6 -> 0.6.8 age adoption passing confidence devDependencies patch
solid-js (source) 1.8.22 -> 1.9.1 age adoption passing confidence dependencies minor
tailwindcss (source) 3.4.12 -> 3.4.13 age adoption passing confidence devDependencies patch
vite (source) 5.4.7 -> 5.4.8 age adoption passing confidence overrides patch
vite (source) 5.4.7 -> 5.4.8 age adoption passing confidence devDependencies patch

Release Notes

solidjs/solid-router (@​solidjs/router)

v0.14.7

Patch Changes
  • 3594e45: fix iterator methods on useSubmissions

v0.14.6

Patch Changes
  • 0a964b6: Fix duplicated push history
  • c61231d: Fix scrollToHash to handle hashes starting with a number
  • 83b7093: remove extra code, fix #​406 slow perf on localeCompare
solidjs/solid-testing-library (@​solidjs/testing-library)

v0.8.10

Compare Source

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.7.0

Compare Source

🚀 Features
  • eslint-plugin: [no-unsafe-call] check calls of Function

  • eslint-plugin: [consistent-type-exports] check export * exports to see if all exported members are types

🩹 Fixes
  • eslint-plugin: properly coerce all types to string in getStaticMemberAccessValue

  • eslint-plugin: [no-deprecated] report on imported deprecated variables

  • eslint-plugin: [no-confusing-non-null-assertion] check !in and !instanceof

❤️ Thank You
  • Abraham Guo
  • auvred
  • Brian Donovan
  • Kirk Waiblinger

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.7.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

JamesIves/github-pages-deploy-action (JamesIves/github-pages-deploy-action)

v4.6.8

Compare Source

What's Changed

Bug Fixes 🐝
  • fix: 🐛 Added the temp deployment directory created by the action to the git safe directory list. This resolves an issue in certain circumstances where the deployment would fail depending on the types of files moved around by the workflow - #​1694.
  • fix: Resolved a rare deployment error where the action would complain that origin/${branch_name} is not a commit and a branch cannot be created from it. The action will continue to attempt to track the origin branch, but if this step fails, it will create a new untracked branch to continue the deployment from. - #​1689.
Testing 🧪
  • test: 🧪 Improved the integration test suite so it now runs immediately post-release to ensure that any issues do no longer in the major version tag (ie @​v4). This was done to combat problems raised by #​1697.

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.8

v4.6.7

Compare Source

What's Changed

Bug Fixes 🐝
  • fix: resolved an issue where main.js was not found in the v4 major tag.

v4.6.6

Compare Source

v4.6.5

Compare Source

What's Changed

What's Changed

Bug Fixes 🐝
  • fix: resolved an issue where the full working directory was not properly getting added to the safe directory list, preventing deployments in certain circumstances.

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.5

tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss)

v0.6.8

Compare Source

v0.6.7

Compare Source

  • Improved performance with large Svelte, Liquid, and Angular files (#​312)
  • Add support for @plugin and @config in v4 (#​316)
  • Add support for Tailwind CSS v4.0.0-alpha.25 (#​317)
solidjs/solid (solid-js)

v1.9.0: - LGTM!

Compare Source

This release like the last is focusing on small quality of life improvements and adjustments that will help us move towards 2.0. So while not the most exciting release to everyone it provides some really important features and fixes to some developers.

And unlike many previous releases the vast majority of the work and features came from PRs from the community. So really all I can say is Looks Good to Me!

Better JSX Validation

While still incomplete across templates we've added JSDOM to the compiler to better detect invalid HTML at build time by comparing what we expect the template to be with what a browser would output. This now includes things that are nested we didn't detect before like putting <a> inside other <a> tags which will lead to the browser "correcting" it in less than intuitive ways.

Improved Exports

While each environment in solid-js/web has its own methods to be used in the compiler. We are now exporting the client methods from the server to prevent weird import errors. Now these methods will throw if used in this environment but shouldn't break your build.

Additionally we have seen some issues in bundlers that incorrectly feed our ESM exports back through the browser field. While this is a known issue they all pointed issues at each other and with no intention of fixing it. We have removed the browser field in this release, meaning some legacy packages may have issues resolving browser if they don't support export conditions.

This is regretful but this blocked deployments on several platforms and since this was the only fix at our disposal after two years of attempting to push this issue to the bundlers to no avail, we've moved forward with it.

Custom Element improvements

We have a few improvements to our custom element support in this release. First off we now detect elements with the is attribute as custom elements which means all the special behavior is afforded to them.

We've also improved our event handler delegating retargetting to better handle shadow DOM events. There were cases where we skipped over part of the tree.

Finally we've added the bool: attribute namespace to handle explicitly setting certain attributes according to boolean attribute rules. While this isn't necessary for built-in booleans currently we handle most attributes as properties and we lacked a specific override. But now we have it:

<my-element bool:enable={isEnabled()}></my-element>

Support for handleEvent Syntax in Non-Delegated Events

A little known thing is that events actually also support objects instead of functions (See: https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)

We(thanks @​titoBouzout) realized we can use this mechanism as a way to set advanced rules like passive or capture on this object as way to handle all current and future event attributes that browsers might add. This way we don't need specific mechanisms like oncapture: (which is now deprecated).

Instead using on: you can set the event properties you wish.

<>
  <div on:click={{
    handleEvent(e) {
      console.log("clicked", e)
    },
    once:true
  }/>
  <div on:wheel={{
    handleEvent(e) {
      e.preventDefault() // only works on not passive events
      e.stopPropagation()  
      console.log("wheel stopped?")
    },
    passive: false
  }} />
</>

Other Updates

We've fixed an issue with lazy images. Apparently, cloneNode doesn't handle them properly so we've updated our heuristic to treat templates with lazy images to be handled with importNode.

We've improved our Hydration Mismatch Error to output the template of that it can't find the matching ID for. This should make it easier to track down where the hydration errors are occurring. There have been several hydration improvements over the later 1.8 releases so upgrading will likely improve the situation for those who have been facing issues.

Finally, we've improved some of the types in the JSX and Signal Setter in this release.


Big thanks to those who contributed to this release: @​wkelly17, @​olivercoad, @​titoBouzout, @​trusktr, @​Huliiiiii. And thanks to all of you who gave feedback on the Metadata/Head Tag RFC. While it didn't make it in this time around you've definitely given us stuff to consider for its future design.

Best,
@​ryansolid

v1.8.23

Compare Source

tailwindlabs/tailwindcss (tailwindcss)

v3.4.13

Compare Source

Fixed
  • Improve source glob verification performance (#​14481)
vitejs/vite (vite)

v5.4.8

Compare Source

Please refer to CHANGELOG.md for details.


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Sep 30, 2024
@renovate renovate bot enabled auto-merge (squash) September 30, 2024 00:43
@renovate renovate bot merged commit cf12076 into main Sep 30, 2024
1 check passed
@renovate renovate bot deleted the renovate/all-minor-patch branch September 30, 2024 00:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants