fix(deps): update all dependencies j:cdx-227 #355
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:
2.5.2
->2.6.2
20.17.6
->20.17.16
16.4.5
->16.4.7
9.1.6
->9.1.7
15.2.10
->15.4.3
3.1.7
->3.1.9
4.0.2
->4.1.0
3.3.3
->3.4.2
0.26.11
->0.27.6
5.6.3
->5.7.3
3.23.8
->3.24.1
Release Notes
coveo/semantic-monorepo-tools (@coveo/semantic-monorepo-tools)
v2.6.2
Compare Source
Bug Fixes
v2.6.1
Compare Source
v2.6.0
Compare Source
Features
2.5.9 (2024-12-02)
2.5.8 (2024-12-02)
2.5.7 (2024-11-25)
2.5.6 (2024-11-18)
2.5.5 (2024-11-18)
2.5.4 (2024-11-11)
2.5.3 (2024-11-04)
2.5.2 (2024-11-04)
2.5.1 (2024-11-01)
v2.5.9
Compare Source
v2.5.8
Compare Source
v2.5.7
Compare Source
v2.5.6
Compare Source
v2.5.5
Compare Source
v2.5.4
Compare Source
v2.5.3
Compare Source
motdotla/dotenv (dotenv)
v16.4.7
Compare Source
Changed
.tap
folder when publishing. (oops, sorry about that everyone. - @motdotla) #848v16.4.6
Compare Source
Changed
typicode/husky (husky)
v9.1.7
Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.1.6...v9.1.7
lint-staged/lint-staged (lint-staged)
v15.4.3
Compare Source
Patch Changes
cbfed1d
Thanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.v15.4.2
Compare Source
Patch Changes
8827ebf
Thanks @iiroj! - Change lint-staged's dependencies to use caret (^
) ranges instead of tilde (~
). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.v15.4.1
Compare Source
Patch Changes
#1504
1c7a45e
Thanks @iiroj! - Default TypeScript config filenames match JS equivalents.#1504
9cc18c9
Thanks @iiroj! - Add missing conditional exports syntax for TypeScript types.v15.4.0
Compare Source
Minor Changes
#1500
a8ec1dd
Thanks @iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:It's also possible to use the
.ts
file extension for the configuration if your Node.js version supports it. The--experimental-strip-types
flag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.Patch Changes
9b79364
Thanks @iiroj! - Handle possible failures when logging user shell for debug info.v15.3.0
Compare Source
Minor Changes
#1495
e69da9e
Thanks @iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.#1493
fa0fe98
Thanks @iiroj! - Added more help messages around the automaticgit stash
that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.For example:
where the backup can be seen with
git show 20addf8
, orgit stash list
:v15.2.11
Compare Source
Patch Changes
#1484
bcfe309
Thanks @wormsik! - Escape paths containing spaces when using the "shell" option.#1487
7dd8caa
Thanks @iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.remy/nodemon (nodemon)
v3.1.9
Compare Source
Bug Fixes
exitcrash
(9c9de6e)v3.1.8
Compare Source
Bug Fixes
octokit/octokit.js (octokit)
v4.1.0
Compare Source
Features
@octokit/plugin-rest-endpoint-methods
(#2788) (2107d79)v4.0.3
Compare Source
Bug Fixes
@octokit/app
and@octokit/types
(#2763) (33d03d9)prettier/prettier (prettier)
v3.4.2
Compare Source
diff
Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)
Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.
U+30A0 can be used as the replacement of the
-
in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン=サーンス”).Fix comments print on class methods with decorators (#16891 by @fisker)
Fix non-idempotent formatting (#16899 by @seiyab)
This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.
v3.4.1
Compare Source
diff
Remove unnecessary parentheses around assignment in
v-on
(#16887 by @fisker)<!-- Input --> <template> <button @​click="foo += 2">Click</button> </template> <!-- Prettier 3.4.0 --> <template> <button @​click="(foo += 2)">Click</button> </template> <!-- Prettier 3.4.1 --> <template> <button @​click="foo += 2">Click</button> </template>
v3.4.0
Compare Source
diff
🔗 Release Notes
TypeStrong/TypeDoc (typedoc)
v0.27.6
Compare Source
Features
ignoredHighlightLanguages
option to specify languages which will beallowed in code blocks but not highlighted, #2819.
Bug Fixes
@include
and@includeCode
now work in the readme file, #2814.same symbol over type literal properties within function parameters.
v0.27.5
Compare Source
Bug Fixes
deeply nested properties. This only affects links to properties of
properties of types, which did not have a clickable link exposed so are
unlikely to have been linked to. Furthermore, these links were not always
created by TypeDoc, only being created if all parent properties contained
comments, #2808.
rendered document and the parent property/page will be linked to instead,
#2808. These warnings can be disabled with the
validation.rewrittenLink
option.
https://
links under thehostedBaseUrl
option's URL will nolonger be treated as external, #2809.
Thanks!
v0.27.4
Compare Source
Features
Converter.EVENT_CREATE_PROJECT
event which fires when a project is created by the converter, #2800.Bug Fixes
@include
and@includeCode
now work for comments on the entry point for projects with a single entry point, #2800.@summary
now works to describe functions within modules, #2803.v0.27.3
Compare Source
Features
Bug Fixes
highlightLanguages
option now permits Shiki aliases to be specified rather than just the language ID, #2798.Thanks!
v0.27.2
Compare Source
Bug Fixes
v0.27.1
Compare Source
Bug Fixes
@categoryDescription
and@groupDescription
on module pages, #2787.v0.27.0
Compare Source
Breaking Changes
result in a different file name structure, #2714.
have changed. They can be partially restored to the previous format by
setting
--sluggerConfiguration.lowercase false
. This change was made tomore closely match the default behavior of GitHub's markdown rendering and
VSCode's autocomplete when creating a relative link to an external markdown
file.
hideParameterTypesInTitle
option, this was originally added asa workaround for many signatures overflowing the available horizontal space
in rendered pages. TypeDoc now has logic to wrap types/signatures smartly,
so this option is no longer necessary.
kindSortOrder
to put references last.sort
order to usealphabetical-ignoring-documents
instead of
alphabetical
.suppressCommentWarningsInDeclarationFiles
totrue
(e.g.
X
, notnew X
)@group
,@category
,@groupDescription
and@categoryDescription
will no longer be removed from the reflections they are present on. They are
skipped during rendering with the
notRenderedTags
option.Features
package.json
exports if theyare not provided manually, #1937.
#anchor
links toreference a heading within them.
@param
comments with nested object types, #2555.@param
comments which reference a typealias/interface. Important properties on the referenced type can now be
highlighted with
@param options.foo
, which will result in the additionalnote being included under the documentation for that parameter, #2147. Note:
This feature is limited to references. It is not supported on other types of
types.
outputs
option which is an array of outputs. This can be usedto render the documentation multiple times with different rendering options
or output types, #2597.
@expand
tag which can be placed on type aliases andinterfaces. When a type with
@expand
is referenced and TypeDoc has a placeto include additional details about the type, the properties of the type
will be included in the page where
@expand
is found. Note that use of thistag can significantly increase the size of your generated documentation if
it is applied to commonly used types as it will result in inlining the
comments for those types everywhere they are referenced, #2303.
@inline
tag which can be placed on type aliases andinterfaces. When a type with
@inline
is referenced, TypeDoc will resolvethe referenced type and convert the type as if it was included directly
within the referencing type. Note that use of this tag can significantly
increase the size of your generated documentation if it is applied to
commonly used types as it will result in inlining the comments for those
types everywhere they are referenced, #2303.
@useDeclaredType
tag for type aliases which can sometimesimprove their documentation, #2654.
@mergeModuleWith
tag which can be used to tell TypeDoc toplace a module/namespace's children under a different module/namespace and
remove the real parent, #2281.
@include
and@includeCode
inline tags to include files withincomments/documents.
notRenderedTags
option. This option is similar to theexcludeTags
option, but while
excludeTags
will result in the tag being completelyremoved from the documentation,
notRenderedTags
only prevents it frombeing included when rendering.
groupReferencesByType
option.navigation.excludeReferences
optionuseFirstParagraphOfCommentAsSummary
option to configure how TypeDochandles comments for module members without the
@summary
tag.favicon
option to specify a.ico
or.svg
favicon to reference.together and will expand/collapse together, #2335.
app.outputs
object for defining new output strategies.@layer typedoc
, #2782.Bug Fixes
readonly
index signatures.overloads if present, #2718.
@enum
if the type was declared before the variable, #2719.declared inside
declare global
, #2774declare module "foo"
as a module rather than a namespace, #2778.cases. This primarily affected destructured parameters.
yaml
to the highlight languages supported by default.txt
as an alias oftext
to indicate a code blockshould not be highlighted.
@ignore
or@hidden
but still referenced byother types will no longer produce warnings about not being exported.
module when resolving
@link
tags.JavaScript is disabled.
rather than when converting. This prevents issues where boosts used by just
one package were incorrectly reported as unused when running with
entryPointStrategy set to packages.
Thanks!
microsoft/TypeScript (typescript)
v5.7.3
: TypeScript 5.7.3Compare Source
For release notes, check out the release announcement.
Downloads are available on npm
v5.7.2
: TypeScript 5.7Compare Source
For release notes, check out the release announcement.
Downloads are available on:
colinhacks/zod (zod)
v3.24.1
Compare Source
Commits:
0c6cbbd
Undeprecate .nonempty()4e219d6
Bump min TS version to 5.065adeea
v3.24.1v3.24.0
Compare Source
Implement
@standard-schema/spec
This is the first version of Zod to implement the Standard Schema spec. This is a new community effort among several validation library authors to implement a common interface, with the goal of simplifying the process of integrating schema validators with the rest of the ecosystem. Read more about the project and goals here.
z.string().jwt()
Thanks to @Mokshit06 and @Cognition-Labs for this contribution!
To verify that a string is a valid 3-part JWT.
To constrain the JWT to a specific algorithm:
z.string().base64url()
Thank you to @marvinruder!
To complement the JWT validation, Zod 3.24 implements a standalone
.base64url()
string validation API. (The three elements of JWTs are base64url-encoded JSON strings.)This functionality is available along the standard
z.string().base64()
validator added in Zod 3.23.z.string().cidr()
Thanks to @wataryooou for their work on this!
A validator for CIDR notation for specifying IP address ranges, e.g.
192.24.12.0/22
.To specify an IP version:
View the full diff from 3.23.8: colinhacks/zod@v3.23.8...v3.24.0
294f54f
Update README_ZH.md about Discriminated unions (#3493)1247caf
Add Kubb as X-to-Zod community tool (#3508)62b7842
Update default branchc6bc80d
Fix issue #3582 : ULID should be case insensitive (#3593)a5b9dc3
docs: add zod-schema-faker to ecosystem (#3605)9818d0e
Add zod-sockets (#3609)7173d0b
Add drizzle-zod library to X to Zod README.md section (#3648)c5a4edc
Add 'schemql' in Powered by Zod (#3800)85916b3
docs: add zod-form-renderer to form integration docs (#3697)51f1dc3
docs: add unplugin-environment in powered by zod (#3778)8e74db3
fix: ipv6 regex validation (#3513)1f4f0da
refactor: rename ip version types (#3755)f487d74
Remove faulty ip test case48f1c47
docs: Remove invalid semicolon in ERROR_HANDLING.md (#3857)1d0a4b9
fix: bigint coerce crash (#3822)14dceaa
Add API library (#3814)f82f817
feat: z.string.cidr() - support CIDR notation (#3820)71a0c33
docs: add info on unqualified local datetime strings (#3760)b85686a
Add support forbase64url
strings (#3712)6407bed
Allow creation of discriminated unions with a readonly array of options (#3535)3755146
Remove createParams cascade from .array() (#3530)963386d
Fix lint69a1798
Implement Standard Schema spec (#3850)c1dd537
Addsfrrm
package to documentation (#3818)b68c05f
feat: Add JWT string validator (#3893)Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone America/Toronto, Automerge - "after 9:00am and before 12:00pm on tuesday, wednesday, thursday" in timezone America/Toronto.
🚦 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 has been generated by Renovate Bot.