-
Notifications
You must be signed in to change notification settings - Fork 0
fix(deps): update minor dependencies #88
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e17a000
to
29283d5
Compare
29283d5
to
4ea04dc
Compare
624f97e
to
4ea04dc
Compare
d95b2c7
to
9458635
Compare
248ed4d
to
9458635
Compare
9458635
to
f4b040c
Compare
e260273
to
76399d6
Compare
dc28528
to
1a013a8
Compare
1a013a8
to
cdeba82
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.4.0
->3.5.0
1.2.0
->1.3.0
4.0.17
->4.1.4
9.23.0
->9.25.1
10.6.1
->10.9.0
4.0.17
->4.1.4
Release Notes
nuxt/content (@nuxt/content)
v3.5.0
Compare Source
Features
Bug Fixes
/__nuxt_content
paths. (#3299) (849e79d)body
changes (#3283) (b6a30aa)nuxt/eslint (@nuxt/eslint)
v1.3.0
Compare Source
🚀 Features
View changes on GitHub
tailwindlabs/tailwindcss (@tailwindcss/vite)
v4.1.4
Compare Source
Added
@tailwindcss/oxide-wasm32-wasi
target for running Tailwind in browser environments like StackBlitz (#17558)Fixed
color-mix(…)
polyfills do not cause used CSS variables to be removed (#17555)color-mix(…)
polyfills create fallbacks for theme variables that reference other theme variables (#17562){10..0..5}
and{0..10..-5}
(#17591)skew-*
utilities (#17627)shadow-inherit
,inset-shadow-inherit
,drop-shadow-inherit
, andtext-shadow-inherit
inherit the shadow color (#17647)fontSize
JS theme keys (#17630)fontSize
array tuple syntax to CSS theme variables (#17630)v4.1.3
Compare Source
Fixed
--value(…)
(#17464)%w
syntax in Slim templates (#17557)v4.1.2
Compare Source
Fixed
@layer base
to polyfill@property
(#17506)drop-shadow-*
utilities that are defined with multiple shadows (#17515)@tailwind utilities
are processed (#17514)color-mix(…)
polyfill creates fallbacks even when using colors that cannot be statically analyzed (#17513)@tailwindcss/vite
and@tailwindcss/postscss
(especially on Windows) (#17511)v4.1.1
Compare Source
Fixed
@source inline(…)
brace expansion (#17491)@import
and body-less@layer
(#17493)@tailwindcss/cli
does not contain an import forjiti
(#17502)v4.1.0
Compare Source
Added
details-content
variant (#15319)inverted-colors
variant (#11693)noscript
variant (#11929, #17431)items-baseline-last
andself-baseline-last
utilities (#13888, #17476)pointer-none
,pointer-coarse
, andpointer-fine
variants (#16946)any-pointer-none
,any-pointer-coarse
, andany-pointer-fine
variants (#16941)user-valid
anduser-invalid
variants (#12370)wrap-anywhere
,wrap-break-word
, andwrap-normal
utilities (#12128)@source inline(…)
and@source not inline(…)
(#17147)@source not "…"
(#17255)text-shadow-*
utilities (#17389)mask-*
utilities (#17134)bg-{position,size}-*
utilities for arbitrary values (#17432)shadow-*/<alpha>
,inset-shadow-*/<alpha>
,drop-shadow-*/<alpha>
, andtext-shadow-*/<alpha>
utilities to control shadow opacity (#17398, #17434)drop-shadow-<color>
utilities (#17434)Fixed
@source
directives (#17391)@tailwindcss/cli
(#17255)content
rules in legacy JavaScript configuration (#17255)@("@​")md:…
as@md:…
in Razor files (#17427)--theme(…)
function still resolves to the CSS variables when using legacy JS plugins (#17458)Changed
node_modules
by default (can be overridden by@source …
rules) (#17255)@source
rules that include file extensions or point insidenode_modules/
folders no longer consider your.gitignore
rules (#17255)bg-{left,right}-{top,bottom}
in favor ofbg-{top,bottom}-{left,right}
utilities (#17378)object-{left,right}-{top,bottom}
in favor ofobject-{top,bottom}-{left,right}
utilities (#17437)eslint/eslint (eslint)
v9.25.1
Compare Source
v9.25.0
Compare Source
v9.24.0
Compare Source
pnpm/pnpm (pnpm)
v10.9.0
Compare Source
Minor Changes
Added support for installing JSR packages. You can now install JSR packages using the following syntax:
or with a version range:
For example, running:
will add the following entry to your
package.json
:When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:
Related issue: #8941.
Note: The
@jsr
scope defaults to https://npm.jsr.io/ if the@jsr:registry
setting is not defined.Added a new setting,
dangerouslyAllowAllBuilds
, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this topnpm-workspace.yaml
:dangerouslyAllowAllBuilds
has the same effect but also allows to be set globally via:It can also be set when running a command:
Patch Changes
verifyDepsBeforeRun
whennodeLinker
ishoisted
and there is a workspace package without dependencies andnode_modules
directory #9424.verifyDepsBeforeRun
support fornodeLinker: pnp
. CombiningverifyDepsBeforeRun
andnodeLinker: pnp
will now print a warning.v10.8.1
Compare Source
Patch Changes
package.json
,onlyBuiltDependencies
will be written topnpm-workspace.yaml
file #9404.v10.8.0
Compare Source
Minor Changes
Experimental. A new hook is supported for updating configuration settings. The hook can be provided via
.pnpmfile.cjs
. For example:Now you can use the
pnpm add
command with the--config
flag to install new configurational dependencies #9377.Patch Changes
!/
inpnpm-workspace.yaml
. This fixes a regression introduced by #9169.pnpm audit --fix
should update the overrides inpnpm-workspace.yaml
.pnpm link
should update overrides inpnpm-workspace.yaml
, not inpackage.json
#9365.v10.7.1
: pnpm 10.7.1Compare Source
Patch Changes
pnpm config set
should convert the settings to their correct type before adding them topnpm-workspace.yaml
#9355.pnpm config get
should read auth related settings via npm CLI #9345.~/
in a path in.npmrc
with the home directory #9217.Platinum Sponsors
Gold Sponsors
v10.7.0
Compare Source
Minor Changes
pnpm config get
andlist
also show settings set inpnpm-workspace.yaml
files #9316.It should be possible to use env variables in
pnpm-workspace.yaml
setting names and value.Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range
*
is the same as name-only, except that patch application failure will not be ignored.For example:
The above configuration would apply
patches/foo-3.patch
to[email protected]
,patches/foo-2.patch
to allfoo
versions which satisfy^2.0.0
except2.1.0
, andpatches/foo-1.patch
to the remainingfoo
versions.pnpm config set --location=project
saves the setting to apnpm-workspace.yaml
file if no.npmrc
file is present in the directory #9316.Rename
pnpm.allowNonAppliedPatches
topnpm.allowUnusedPatches
. The old name is still supported but it would print a deprecation warning message.Add
pnpm.ignorePatchFailures
to manage whether pnpm would ignore patch application failures.If
ignorePatchFailures
is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.If
ignorePatchFailures
is explicitly set tofalse
, pnpm would throw an error when any type of patch fails to apply.If
ignorePatchFailures
is explicitly set totrue
, pnpm would print a warning when any type of patch fails to apply.Patch Changes
v10.6.5
Compare Source
v10.6.4
: pnpm 10.6.4Compare Source
Patch Changes
pnpm dlx
with--allow-build
flag #9263.use-node-version
should not cause pnpm itself to break #9276.Platinum Sponsors
Gold Sponsors
v10.6.3
Compare Source
Patch Changes
pnpm install --prod=false
should not crash, when executed in a project with apnpm-workspace.yaml
file #9233. This fixes regression introduced via #9211.Add the missing
node-options
config torecursive run
#9180.Removed a branching code path that only executed when
dedupe-peer-dependents=false
. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that overridededupe-peer-dependents
to false. There should be less unique bugs from turning offdedupe-peer-dependents
.See details in #9259.
v10.6.2
Compare Source
Patch Changes
pnpm self-update
should always update the version in thepackageManager
field ofpackage.json
.pnpm patch-commit
will now use the same filesystem as the store directory to compare and create patch files.--loglevel=error
is used.peerDependencyRules
should be set inpnpm-workspace.yaml
to take effect.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.