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 dependencies j:cdx-227 #355

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate-coveo[bot]
Copy link
Contributor

@renovate-coveo renovate-coveo bot commented Nov 18, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@coveo/semantic-monorepo-tools 2.5.2 -> 2.6.2 age adoption passing confidence
@types/node (source) 20.17.6 -> 20.17.16 age adoption passing confidence
dotenv 16.4.5 -> 16.4.7 age adoption passing confidence
husky 9.1.6 -> 9.1.7 age adoption passing confidence
lint-staged 15.2.10 -> 15.4.3 age adoption passing confidence
nodemon (source) 3.1.7 -> 3.1.9 age adoption passing confidence
octokit 4.0.2 -> 4.1.0 age adoption passing confidence
prettier (source) 3.3.3 -> 3.4.2 age adoption passing confidence
typedoc (source) 0.26.11 -> 0.27.6 age adoption passing confidence
typescript (source) 5.6.3 -> 5.7.3 age adoption passing confidence
zod (source) 3.23.8 -> 3.24.1 age adoption passing confidence

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
  • git: allow additional args on gitDiff and getSHA1FromRef (#​277) (504db98)

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
  • Ignore .tap folder when publishing. (oops, sorry about that everyone. - @​motdotla) #​848

v16.4.6

Compare Source

Changed
  • Clean up stale dev dependencies #​847
  • Various README updates clarifying usage and alternative solutions using dotenvx
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
  • #​1512 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
  • #​1509 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

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:

    /**
     * @​filename: lint-staged.config.js
     * @​type {import('lint-staged').Configuration}
     */
    export default {
      '*': 'prettier --write',
    }

    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.

    export NODE_OPTIONS="--experimental-strip-types"
    
    npx lint-staged --config lint-staged.config.ts
Patch Changes

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 automatic git 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:

    % npx lint-staged
    ✔ Backed up original state in git stash (20addf8)
    ✔ Running tasks for staged files...
    ✔ Applying modifications from tasks...
    ✔ Cleaning up temporary files...
    

    where the backup can be seen with git show 20addf8, or git stash list:

    % git stash list
    stash@{0}: lint-staged automatic backup (20addf8)
    

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
  • maintain backward support for exitcrash (9c9de6e)

v3.1.8

Compare Source

Bug Fixes
octokit/octokit.js (octokit)

v4.1.0

Compare Source

Features
  • deps: bump Octokit deps to fix Deno compatibility, new endpoints via @octokit/plugin-rest-endpoint-methods (#​2788) (2107d79)

v4.0.3

Compare Source

Bug Fixes
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.

<!-- Input (--prose-wrap=never) -->

C言
語
・
C++
・
Go
・
Rust

<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust

<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

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)
// Input
class A {
  @&#8203;decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.1
class A {
  @&#8203;decorator
  async /**
   * The method description
   *
   */
  method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.2
class A {
  @&#8203;decorator
  /**
   * The method description
   *
   */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}
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.

// Input
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.1 (first)
<div>
  foo
  <span>
    longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo
  </span>, abc
</div>;

// Prettier 3.4.1 (second)
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.2
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

v3.4.1

Compare Source

diff

Remove unnecessary parentheses around assignment in v-on (#​16887 by @​fisker)
<!-- Input -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @&#8203;click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

v3.4.0

Compare Source

diff

🔗 Release Notes

TypeStrong/TypeDoc (typedoc)

v0.27.6

Compare Source

Features
  • Added ignoredHighlightLanguages option to specify languages which will be
    allowed in code blocks but not highlighted, #​2819.
Bug Fixes
  • @include and @includeCode now work in the readme file, #​2814.
  • TypeDoc will now avoid making references to references, #​2811.
  • Fixed output specific option specification, #​2818.
  • Improved type reference conversion to avoid including defaulted type arguments, #​2820.
  • Fixed parsing of declaration references which include a module and a local reference, #​2810.
  • Improved link resolution logic to prioritize type alias properties with the
    same symbol over type literal properties within function parameters.

v0.27.5

Compare Source

Bug Fixes
  • Possibly Breaking: TypeDoc will no longer render anchors within the page for
    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.
  • TypeDoc will now warn if a property which does not have a URL within the
    rendered document and the parent property/page will be linked to instead,
    #​2808. These warnings can be disabled with the validation.rewrittenLink
    option.
  • Fix restoration of groups/categories including documents, #​2801.
  • Fixed missed relative paths within markdown link references in documents.
  • Improved handling of incomplete inline code blocks within markdown.
  • Direct https:// links under the hostedBaseUrl option's URL will no
    longer be treated as external, #​2809.
Thanks!

v0.27.4

Compare Source

Features
  • API: Introduced new Converter.EVENT_CREATE_PROJECT event which fires when a project is created by the converter, #​2800.
Bug Fixes
  • Switch from gzip to deflate for compressing assets to make output consistent across different operating systems, #​2796.
  • @include and @includeCode now work for comments on the entry point for projects with a single entry point, #​2800.
  • Cascaded modifier tags will no longer be copied into type literals, #​2802.
  • @summary now works to describe functions within modules, #​2803.
  • Corrected navigation showing module link as current when not on module page, #​2805.

v0.27.3

Compare Source

Features
  • Added support for PNG favicons, #​2790.
  • Improved support for hosting TypeDoc with strict Content Security Policy rules, #​2794.
Bug Fixes
  • Add special handling for import types with type errors discarded with ts-expect-error, #​2792.
  • Fixed low contrast in default colors for properties/accessors in light mode, #​2795.
  • The highlightLanguages option now permits Shiki aliases to be specified rather than just the language ID, #​2798.
Thanks!

v0.27.2

Compare Source

Bug Fixes
  • Fix crash with TypeScript 5.5.x, #​2789.

v0.27.1

Compare Source

Bug Fixes
  • Include classes which inherit from another package in class hierarchy in packages mode, #​2467.
  • Fixed handling of @categoryDescription and @groupDescription on module pages, #​2787.
  • Fixed automatic discovery of entry points in packages mode.
  • Reverted accidental style change for hierarchy page introduced in 0.27.0
  • The hierarchy Expand/Collapse link will now only appear if the hierarchies are different.

v0.27.0

Compare Source

Breaking Changes
  • Convert to ESM to enable easier use of ESM-only dependencies.
  • Drop support for TypeScript <5.0, no longer supported by DefinitelyTyped
  • Relaxed requirements for file names and generated url fragments. This may
    result in a different file name structure, #​2714.
  • Anchors to document headings and reflections within a HTML generated pages
    have changed. They can be partially restored to the previous format by
    setting --sluggerConfiguration.lowercase false. This change was made to
    more closely match the default behavior of GitHub's markdown rendering and
    VSCode's autocomplete when creating a relative link to an external markdown
    file.
  • Removed the hideParameterTypesInTitle option, this was originally added as
    a 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.
  • Changed the default kindSortOrder to put references last.
  • Changed the default sort order to use alphabetical-ignoring-documents
    instead of alphabetical.
  • Changed default of suppressCommentWarningsInDeclarationFiles to true
  • API: Constructor signatures now use the parent class name as their name
    (e.g. X, not new X)
  • API: @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
  • Add support for TypeScript 5.7
  • TypeDoc will now discover entry points from package.json exports if they
    are not provided manually, #​1937.
  • Relative links to markdown files may now include #anchor links to
    reference a heading within them.
  • Improved support for @param comments with nested object types, #​2555.
  • Improved support for @param comments which reference a type
    alias/interface. Important properties on the referenced type can now be
    highlighted with @param options.foo, which will result in the additional
    note 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.
  • Added a new outputs option which is an array of outputs. This can be used
    to render the documentation multiple times with different rendering options
    or output types, #​2597.
  • Added support for rendering alerts (or callouts) in markdown.
  • Add support for an @expand tag which can be placed on type aliases and
    interfaces. When a type with @expand is referenced and TypeDoc has a place
    to 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 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.
  • Add support for an @inline tag which can be placed on type aliases and
    interfaces. When a type with @inline is referenced, TypeDoc will resolve
    the 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.
  • Introduced a new @useDeclaredType tag for type aliases which can sometimes
    improve their documentation, #​2654.
  • Added a new @mergeModuleWith tag which can be used to tell TypeDoc to
    place a module/namespace's children under a different module/namespace and
    remove the real parent, #​2281.
  • Added new @include and @includeCode inline tags to include files within
    comments/documents.
  • Add notRenderedTags option. This option is similar to the excludeTags
    option, but while excludeTags will result in the tag being completely
    removed from the documentation, notRenderedTags only prevents it from
    being included when rendering.
  • Added groupReferencesByType option.
  • Added navigation.excludeReferences option
  • Added useFirstParagraphOfCommentAsSummary option to configure how TypeDoc
    handles comments for module members without the @summary tag.
  • Introduced favicon option to specify a .ico or .svg favicon to reference.
  • Sections within the page and in the "On This Page" navigation are now tied
    together and will expand/collapse together, #​2335.
  • API: Introduced a new app.outputs object for defining new output strategies.
  • API: TypeDoc's CSS is now wrapped in @layer typedoc, #​2782.
Bug Fixes
  • TypeDoc now properly flags readonly index signatures.
  • TypeDoc will now use the first signature's comment for later signatures in
    overloads if present, #​2718.
  • Fixed handling of @enum if the type was declared before the variable, #​2719.
  • Fixed empty top level modules page in packages mode, #​2753.
  • TypeDoc can now link to type alias properties, #​2524.
  • TypeDoc will now document the merged symbol type when considering globals
    declared inside declare global, #​2774
  • TypeDoc now converts declare module "foo" as a module rather than a namespace, #​2778.
  • Import types in type aliases now use module member references if present, #​2779.
  • Fixed an issue where properties were not properly marked optional in some
    cases. This primarily affected destructured parameters.
  • Added yaml to the highlight languages supported by default.
  • TypeDoc now recognizes txt as an alias of text to indicate a code block
    should not be highlighted.
  • Items which are hidden with @ignore or @hidden but still referenced by
    other types will no longer produce warnings about not being exported.
  • If a project only has one module within it, TypeDoc will now consider that
    module when resolving @link tags.
  • The arrows to indicate whether or not a section is open now work when
    JavaScript is disabled.
  • Group/category search boosts are now applied when writing the search index
    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.3

Compare Source

For release notes, check out the release announcement.

Downloads are available on npm

v5.7.2: TypeScript 5.7

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

colinhacks/zod (zod)

v3.24.1

Compare Source

Commits:

v3.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.

z.string().jwt();

⚠️ This does not verify your JWT cryptographically! It merely ensures its in the proper format. Use a library like jsonwebtoken to verify the JWT signature, parse the token, and read the claims.

To constrain the JWT to a specific algorithm:

z.string().jwt({ alg: "RS256" });

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.)

z.string().base64url()

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.

z.string().cidr()

To specify an IP version:

z.string().cidr({ version: "v4" })
z.string().cidr({ version: "v6" })

View the full diff from 3.23.8: colinhacks/zod@v3.23.8...v3.24.0


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.


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

This PR has been generated by Renovate Bot.

@renovate-coveo renovate-coveo bot requested a review from a team as a code owner November 18, 2024 05:00
@renovate-coveo renovate-coveo bot requested review from y-lakhdar, louis-bompart and fbeaudoincoveo and removed request for a team November 18, 2024 05:00
@renovate-coveo renovate-coveo bot changed the title chore(deps): update dependency @coveo/semantic-monorepo-tools to v2.5.3 j:cdx-227 chore(deps): update dependency @coveo/semantic-monorepo-tools to v2.5.4 j:cdx-227 Nov 18, 2024
@renovate-coveo renovate-coveo bot changed the title chore(deps): update dependency @coveo/semantic-monorepo-tools to v2.5.4 j:cdx-227 chore(deps): update dependency @coveo/semantic-monorepo-tools to v2.5.6 j:cdx-227 Nov 25, 2024
@renovate-coveo renovate-coveo bot changed the title chore(deps): update dependency @coveo/semantic-monorepo-tools to v2.5.6 j:cdx-227 chore(deps): update all dependencies j:cdx-227 Nov 25, 2024
@renovate-coveo renovate-coveo bot force-pushed the renovate/all branch 9 times, most recently from 429ee4c to b4c6e40 Compare December 5, 2024 06:30
@renovate-coveo renovate-coveo bot force-pushed the renovate/all branch 7 times, most recently from d51f7df to 3e27641 Compare December 11, 2024 06:00
@renovate-coveo renovate-coveo bot force-pushed the renovate/all branch 4 times, most recently from 8fb8999 to 5bc8aa7 Compare December 17, 2024 07:00
@renovate-coveo renovate-coveo bot changed the title chore(deps): update all dependencies j:cdx-227 fix(deps): update all dependencies j:cdx-227 Dec 17, 2024
@renovate-coveo renovate-coveo bot force-pushed the renovate/all branch 6 times, most recently from 0fc9fe4 to 175c686 Compare December 23, 2024 14:00
@renovate-coveo renovate-coveo bot force-pushed the renovate/all branch 3 times, most recently from d97dea2 to d7c7bf7 Compare January 8, 2025 02:00
@renovate-coveo renovate-coveo bot force-pushed the renovate/all branch 4 times, most recently from 738edb8 to cbc4098 Compare January 16, 2025 18:02
@renovate-coveo renovate-coveo bot force-pushed the renovate/all branch 4 times, most recently from b727fca to 4db7e0b Compare January 23, 2025 18:30
@renovate-coveo renovate-coveo bot force-pushed the renovate/all branch 4 times, most recently from 8c6e749 to d4a6d35 Compare January 30, 2025 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants