chore(deps): update all non-major dependencies #8

renovate · 2024-05-27T02:07:13Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@dotenvx/dotenvx	`1.11.4` -> `1.37.0`
arktype (source)	`^2.0.4` -> `^2.1.0`
shadcn-nuxt (source)	`0.10.4` -> `0.11.4`

Release Notes

dotenvx/dotenvx (@dotenvx/dotenvx)

`v1.37.0`

Compare Source

Added

add dotenvx rotate command 🎉 (#530)

also: our whitepaper is released as a draft.

`v1.36.0`

Compare Source

Changed

--strict flag respects (doesn't throw) anything in --ignore flag (#527)

`v1.35.0`

Compare Source

Added

npx dotenvx precommit support as a convenience (#523)
main.get method (#524)

The addition of main.get facilitates what we term Decryption at Access, a concept explored in greater detail in our whitepaper.

`v1.34.0`

Compare Source

Added

main.set method now writes to files (#517)

`v1.33.0`

Compare Source

Added

support ESM import convenience import '@dotenvx/dotenvx/config' (#508)

`v1.32.1`

Compare Source

Changed

remove duplicated help messages (#504)

`v1.32.0`

Compare Source

Added

add encrypted check support for ext prebuild (#501)

Changed

modify ext precommit to check git modified state as well as git staged state - useful for using dotenvx ext precommit without the --install flag in automated scripts and ci. (#499)

Removed

remove internal logger methods errorvp, errorvpb, warnv, warnvp, warnvpb, successvp, successvpb, help2 (#501)

`v1.31.3`

Compare Source

Changed

adjust wingetcreate to use powershell when parsing version

`v1.31.2`

Compare Source

Changed

use wingetcreate for releasing to WinGet (#498)

`v1.31.1`

Compare Source

Changed

🐞 fix encryption of values containing explicit \n newlines (#495)

`v1.31.0`

Compare Source

Added

expose main.set function (#492)
add missing types for main.config (#491)

`v1.30.1`

Compare Source

Added

support complex command substitution combining variable expansion (#490)

`v1.30.0`

Compare Source

Added

add -fk (--env-keys-file) flag to customize the path to your .env.keys file with run, get, set, encrypt, decrypt, and keypair 🎉 (#486)

This is great for monorepos. Maintain one .env.keys file across all your apps.

$ dotenvx encrypt -fk .env.keys -f apps/backend/.env
$ dotenvx encrypt -fk .env.keys -f apps/frontend/.env

$ tree -a .
├── .env.keys
└── apps
    ├── backend
    │   └── .env
    └── frontend
        └── .env

$ dotenvx get -fk .env.keys -f apps/backend/.env

`v1.29.0`

Compare Source

Added

add --ignore flag to suppress specified errors. example: dotenvx run --ignore=MISSING_ENV_FILE (#485)

`v1.28.0`

Compare Source

Changed

.env.keys file is generated WITHOUT quotes going forward. This is to minimize friction around Docker gotchas to developers - old versions of Docker do not support --env-file containing quoted keys/values. (#480) (additional note)

`v1.27.0`

Compare Source

Added

add support for \t expansion when double quoted. (e.g. TAB="hi\tfriend" becomes hi friend) (#479)

`v1.26.2`

Compare Source

Changed

build binaries with bytecode option (#477)

`v1.26.1`

Compare Source

Added

add typescript type definitions for main.parse method (#475)

`v1.26.0`

Compare Source

Added

add privateKey option to main.parse method (#474)

`v1.25.2`

Compare Source

Added

for binaries add pre-build step using esbuild (#471)

Removed

remove types for functions that were removed a while back (2aa660)

`v1.25.1`

Compare Source

Changed

improve helpful error messaging around decryption failures by specifying specific key and private key name (#463)

`v1.25.0`

Compare Source

Added

add run --strict flag to exit with code 1 if any errors are encountered - like a missing .env file or decryption failure (#460)
add get --strict flag to exit with code 1 if any errors are encountered - like a missing .env file or decryption failure (#461)
add strict option to config() to throw for any errors (#459)

Changed

log MISSING_ENV_FILE and DECRYPTION_FAILED errors to stderr (prior was stdout as a warning) (#459)

Removed

remove dotenvx.get() function from lib/main.js. (parse already historically exists for this purpose) (#461)

`v1.24.5`

Compare Source

Changed

🐞 do not expand prior literal values (#458)

`v1.24.4`

Compare Source

Changed

do not expand command substitution (#456)

`v1.24.3`

Compare Source

Changed

🐞 fix command substitution for more complex commands (#455)

`v1.24.2`

Compare Source

Changed

treat pre-existing expandable values as literal in process.env (#450)

`v1.24.1`

Compare Source

Changed

bump cross-spawn to prevent potential ReDoS CVE-2024-21538 (#449)

`v1.24.0`

Compare Source

Added

support progressive append/update (#445)

FOO=foo
FOO=${FOO}bar

`v1.23.0`

Compare Source

Added

deeper variable expansion support and protection against self-referencing variables 🛡️ (#439)

`v1.22.2`

Compare Source

Changed

more lenient handling of -- separator and better error messaging when flags are ambiguous (#438)

`v1.22.1`

Compare Source

Changed

🐞 patch loading order issue with single quotes (#436)

`v1.22.0`

Compare Source

Added

add --pattern argument to ext gitignore (dotenvx ext gitignore --pattern .env.keys) (#430)

Changed

clarify next steps after first time encrypting (#430)

`v1.21.1`

Compare Source

Changed

for --convention nextjs ingnore .env.local for TEST environment (#425)
for precommit redirect missing dotenvx command using POSIX compliant redirection (#424)
make parent dotenvx help command less noisy by removing [options]. run dotenvx COMMAND -h to list all available options like always (#429)

`v1.21.0`

Compare Source

Changed

treat single quotes literally (#423)
respect user chosen quotes (#423 #377)

🎓 now if you choose to single quote, double quote, no quote, or backtick your value it will be respected - including for encrypted values. this more intuitively handles complex cases like escaped characters, literals, and json.

`v1.20.1`

Compare Source

Changed

update eciesjs (#421)
remove default values for ts interface - no longer permitted by latest ts (#419)

`v1.20.0`

Compare Source

Changed

respect process.env.DOTENV_PRIVATE_KEY and/or process.env.DOTENV_PUBLIC_KEY on set (#401)
respect process.env.DOTENV_PRIVATE_KEY and/or process.env.DOTENV_PUBLIC_KEY on encrypt (#411)
respect process.env.DOTENV_PRIVATE_KEY on decrypt (#412)
change logger.help to use brighter blue (#414)

Removed

remove main.decrypt,encrypt,set (#410)

`v1.19.3`

Compare Source

Changed

🐞 fix decrypt re-encrypt of values containing backslashes (#406)

`v1.19.2`

Compare Source

Changed

forward additional signals like SIGUSR2 (#403)

`v1.19.1`

Compare Source

Changed

if SIGTERM or SIGINT sent, don't bubble wrapped process error (#402)

`v1.19.0`

Compare Source

Added

support key glob filtering for encrypt and decrypt. example: dotenvx encrypt -ek "NEXT_PUBLIC_*" (#397)

`v1.18.1`

Compare Source

Added

escape user inputted regex groupings like $1 or $2. (#396)

`v1.18.0`

Compare Source

Added

set and encrypt preserve leading spaces (#395)

     HELLO=world

Changed

improve escape and quote handling for set, encrypt, and decrypt (#395)
🐞 fix encrypt, then decrypt, then encrypt on a json value (#377)

Note: the underlying replace engine to support these changes now wraps your values in single quotes. the prior replace engine wrapped in double quotes.

So where your .env used to look like this with double quotes:

HELLO="encrypted:1234"
API_KEY="encrypted:5678"

It will now begin looking like this with single quotes:

HELLO='encrypted:1234'
API_KEY='encrypted:5678'

It's an aesthetic side effect only. Your values will continue to be decrypted and encrypted correctly.

`v1.17.0`

Compare Source

Added

add --format=eval option for get (#393)

`v1.16.1`

Compare Source

Changed

suppress stderr using options.stdio (#391)

`v1.16.0`

Compare Source

Changed

for dotenvx keypair call out to dotenvx pro keypair if pro installed (#390)

`v1.15.0`

Compare Source

Added

add --format=shell option for keypair (#389)

`v1.14.2`

Compare Source

Changed

swap process.stdout.write for console.log to patch up npx edge case (#387)

`v1.14.1`

Compare Source

Changed

run precommit hook only on staged files (#380)

`v1.14.0`

Compare Source

Added

add dotenvx keypair command for printing your public/private keypairs (#375)

`v1.13.3`

Compare Source

Changed

exit code 1 when decrypt fails in any way (#374)

`v1.13.2`

Compare Source

Added

expose getColor and bold to lib/main.js (#369)

`v1.13.1`

Compare Source

Added

expose logger and setLogLevel to lib/main.js - const = { logger, setLogLevel } = require('@dotenvx/dotenvx') (#368)

`v1.13.0`

Compare Source

Changed

move ls to core commands (#367)

`v1.12.1`

Compare Source

Changed

return without quotations for dotenvx get --format shell (#366)

`v1.12.0`

Compare Source

Added

add dotenvx get --format shell option (#363)

`v1.11.5`

Compare Source

Changed

revert tinyexec for execa - to support usage in bun

arktypeio/arktype (arktype)

`v2.1.0`

Compare Source

`match`

The match function provides a powerful way to handle different types of input and return corresponding outputs based on the input type, like a type-safe switch statement.

Case Record API

The simplest way to define a matcher is with ArkType definition strings as keys with corresponding handlers as values:

import { match } from "arktype"

const sizeOf = match({
	"string | Array": v => v.length,
	number: v => v,
	bigint: v => v,
	default: "assert"
})

// a match definition is complete once a `default` has been specified,
// either as a case or via the .default() method

sizeOf("abc") // 3
sizeOf([1, 2, 3, 4]) // 4
sizeOf(5n) // 5n
// ArkErrors: must be an object, a string, a number or a bigint (was boolean)
sizeOf(true)

In this example, sizeOf is a matcher that takes a string, array, number, or bigint as input. It returns the length of strings and arrays, and the value of numbers and bigints.

default accepts one of 4 values:

"assert": accept unknown, throw if none of the cases match
"never": accept an input based on inferred cases, throw if none match
"reject": accept unknown, return ArkErrors if none of the cases match
(data: In) => unknown: handle data not matching other cases directly

Cases will be checked in the order they are specified, either as object literal keys or via chained methods.

Fluent API

The match function also provides a fluent API. This can be convenient for non-string-embeddable definitions:

// the Case Record and Fluent APIs can be easily combined
const sizeOf = match({
	string: v => v.length,
	number: v => v,
	bigint: v => v
})
	// match any object with a numeric length property and extract it
	.case({ length: "number" }, o => o.length)
	// return 0 for all other data
	.default(() => 0)

sizeOf("abc") // 3
sizeOf({ name: "David", length: 5 }) // 5
sizeOf(null) // 0

Narrowing input with `in`, property matching with `at`

type Data =
	| {
			id: 1
			oneValue: number
	  }
	| {
			id: 2
			twoValue: string
	  }

const discriminateValue = match
	// .in allows you to specify the input TypeScript allows for your matcher
	.in<Data>()
	// .at allows you to specify a key at which your input will be matched
	.at("id")
	.match({
		1: o => `${o.oneValue}!`,
		2: o => o.twoValue.length,
		default: "assert"
	})

discriminateValue({ id: 1, oneValue: 1 }) // "1!"
discriminateValue({ id: 2, twoValue: "two" }) // 3
discriminateValue({ oneValue: 3 })

Builtin keywords can now be globally configured

This can be very helpful for customizing error messages without needing to create your own aliases or wrappers.

import { configure } from "arktype/config"

configure({
	keywords: {
		string: "shorthand description",
		"string.email": {
			actual: () => "definitely fake"
		}
	}
})

import "./config.ts"
import { type } from "arktype"

const user = type({
	name: "string",
	email: "string.email"
})

const out = user({
	// ArkErrors: name must be shorthand description (was a number)
	name: 5,
	// ArkErrors: email must be an email address (was definitely fake)
	email: "449 Canal St"
})

The options you can provide here are identical to those used to configure a Type directly, and can also be extended at a type-level to include custom metadata.

Tuple and args expressions for `.to`

If a morph returns an ArkErrors instance, validation will fail with that result instead of it being treated as a value. This is especially useful for using other Types as morphs to validate output or chain transformations.

To make this easier, there's a special to operator that can pipe to a parsed definition without having to wrap it in type to make it a function.

This was added before 2.0, but now it comes with a corresponding operator (|>) so that it can be expressed via a tuple or args like most other expressions:

const fluentStillWorks = type("string.numeric.parse").to("number % 2")

const nowSoDoesTuple = type({
	someKey: ["string.numeric.parse", "|>", "number % 2"]
})

const andSpreadArgs = type("string.numeric.parse", "|>", "number % 2")

Error configurations now accept a string directly

const customOne = type("1", "@&#8203;", {
	// previously only a function returning a string was allowed here
	message: "Yikes."
})

// ArkErrors: Yikes.
customOne(2)

Keep in mind, as mentioned in the docs, error configs like message can clobber more granular config options like expected and actual and cannot be included in composite errors e.g. for a union.

Though generally, returning a string based on context is the best option, in situations where you always want the same static message, it's now easier to get that!

Type.toString() now wraps its syntactic representation in `Type<..>`

Previously, Type.toString() just returned Type.expression. However, in contexts where the source of a message isn't always a Type, it could be confusing:

// < 2.1.0:  "(was string)"
// >= 2.1.0: "(was Type<string>)"
console.log(`(was ${type.string})`)

Hopefully if you interpolate a Type, you'll be less confused by the result from now on!

Improve how Type instances are inferred when wrapped in external generics

Previously, we used NoInfer in some Type method returns. After migrating those to inlined conditionals, we get the same benefit and external inference for cases like this is more reliable:

function fn<
	T extends {
		schema: StandardSchemaV1
	}
>(_: T) {
	return {} as StandardSchemaV1.InferOutput<T["schema"]>
}

// was inferred as unknown (now correctly { name: string })
const arkRes = fn({
	schema: type({
		name: "string"
	})
})

Fix an issue causing some discriminated unions to incorrectly reject default cases

const discriminated = type({
	id: "0",
	k1: "number"
})
	.or({ id: "1", k1: "number" })
	.or({
		name: "string"
	})

// previously, this was rejected as requiring a "k1" key

// will now hit the case discriminated for id: 1,
// but still correctly be allowed via the { name: string } branch
discriminated({ name: "foo", id: 1 }))

unovue/shadcn-vue (shadcn-nuxt)

`v0.11.4`

Compare Source

CLI

Modified to use updated registry url

🐞 Bug Fixes

Add missing useMediaQuery in SidebarProvider.vue new-york style - by @fabianbernhart in https://github.com/unovue/shadcn-vue/issues/927 (8a24d)
Only apply text-sidebar-foreground to sidebar - by @benkroeger in https://github.com/unovue/shadcn-vue/issues/986 (1195a)
Sidebar not installable in JS projects - by @4m1n0s in https://github.com/unovue/shadcn-vue/issues/1026 (efc4e)
Calendar heading slots typing - by @ZTL-UwU in https://github.com/unovue/shadcn-vue/issues/1038 (772b8)
RadioGroupItem: Add peer class to RadioGroupItem - by @wsehl in https://github.com/unovue/shadcn-vue/issues/1046 (86702)
Sidebar: Component import and registry dependencies - by @zernonia (693b0)
navigation: Add NavigationMenuIndicator export - by @sanskar-mk2 in https://github.com/unovue/shadcn-vue/issues/1012 (5572d)

View changes on GitHub

`v0.11.3`

Compare Source

🐞 Bug Fixes

Module build - by @zernonia (93be7)
Switch from placeholder: to data-placeholder: prefix class for SelectValue - by @damienroche in https://github.com/unovue/shadcn-vue/issues/867 (a5b25)
Add missing classes to button - by @brianle1301 in https://github.com/unovue/shadcn-vue/issues/877 (384c8)
Error in the build of the auto form with Vite and TypeScript #870 - by @louis-va in https://github.com/unovue/shadcn-vue/issues/896 and https://github.com/unovue/shadcn-vue/issues/870 (ac699)
Mobile sidebar component #840 - by @Whbbit1999 and @zernonia in https://github.com/unovue/shadcn-vue/issues/884 and https://github.com/unovue/shadcn-vue/issues/840 (2d5ad)
CLI: Temporarily downgrade package to 3.2.0 due to TSInterfaceHeritage issue - by @leochiu-a and leochiu in https://github.com/unovue/shadcn-vue/issues/913 (16f1d)

View changes on GitHub

`v0.11.2`

Compare Source

Fixes

unovue/shadcn-vue@ff1b5f0
unovue/shadcn-vue@2cb7671
unovue/shadcn-vue@eff3e75
unovue/shadcn-vue@3646203

Full Changelog: unovue/shadcn-vue@v0.11.0...v0.11.2

View changes on GitHub

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 bot force-pushed the renovate/all-minor-patch branch 25 times, most recently from ad28f46 to b3a722a Compare June 3, 2024 07:40

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from d377869 to ef59ce2 Compare June 5, 2024 15:44

renovate bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from 772fe19 to e86de96 Compare February 14, 2025 06:46

renovate bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from b22eef9 to 2b30a00 Compare February 21, 2025 23:33

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 827853b to 18fcd4a Compare February 23, 2025 13:05

chore(deps): update all non-major dependencies

364e536

renovate bot force-pushed the renovate/all-minor-patch branch from 18fcd4a to 364e536 Compare February 23, 2025 17:48

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update all non-major dependencies #8

chore(deps): update all non-major dependencies #8

renovate bot commented May 27, 2024 •

edited

Loading

chore(deps): update all non-major dependencies #8

Are you sure you want to change the base?

chore(deps): update all non-major dependencies #8

Conversation

renovate bot commented May 27, 2024 • edited Loading

Release Notes

Added

Changed

Added

Added

Added

Changed

Added

Changed

Removed

Changed

Changed

Changed

Added

Added

Added

Added

Changed

Added

Changed

Added

Added

Added

Removed

Changed

Added

Changed

Removed

Changed

Changed

Changed

Changed

Changed

Added

Added

Changed

Changed

Added

Changed

Changed

Changed

Changed

Changed

Removed

Changed

Changed

Changed

Added

Added

Added

Changed

Added

Changed

Changed

Added

Changed

Changed

Added

Changed

Added

Added

Changed

Changed

Added

Changed

match

Case Record API

Fluent API

Narrowing input with in, property matching with at

Builtin keywords can now be globally configured

Tuple and args expressions for .to

Error configurations now accept a string directly

Type.toString() now wraps its syntactic representation in Type<..>

Improve how Type instances are inferred when wrapped in external generics

Fix an issue causing some discriminated unions to incorrectly reject default cases

renovate bot commented May 27, 2024 •

edited

Loading

`match`

Narrowing input with `in`, property matching with `at`

Tuple and args expressions for `.to`

Type.toString() now wraps its syntactic representation in `Type<..>`