fix(deps): update minor updates (minor) #170
Open
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Thank you for following the naming conventions! 🙏 |
renovate
bot
force-pushed
the
renovate/minor-updates
branch
from
eed223b to
1b534d1
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/minor-updates
branch
from
1b534d1 to
2b1b5bd
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/minor-updates
branch
4 times, most recently
from
51643e6 to
8252e11
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
4 times, most recently
from
c34105a to
65483fa
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/minor-updates
branch
2 times, most recently
from
606a485 to
0aa6646
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
2 times, most recently
from
183a925 to
ff72759
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
from
ff72759 to
62fec3a
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
2 times, most recently
from
e3071e3 to
de81a15
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
2 times, most recently
from
89d1e30 to
3dcedc2
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
2 times, most recently
from
bb6de21 to
396cf8f
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
2 times, most recently
from
157cfa9 to
821457e
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
2 times, most recently
from
b048a66 to
1b62774
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/minor-updates
branch
2 times, most recently
from
fce587a to
beb5d7b
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
2 times, most recently
from
8040399 to
f7e19c7
Compare
Signed-off-by: Renovate Bot <[email protected]>
renovate
bot
force-pushed
the
renovate/minor-updates
branch
from
f7e19c7 to
de271e5
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:
>=2.2.4->>=2.8.3^15.3.0->^15.5.2^0.2.12->^0.3.12^2.12.0->^2.15.1Release Notes
wanasit/chrono (chrono-node@<2.2.4)
v2.8.3Compare Source
abba434v2.8.2Compare Source
v2.8.1Compare Source
971b833174b35ev2.8.0Compare Source
New/Fix: Reference date calculation on the assigned timezone
4033a27Previously, the reference date calculation (e.g., "1 day ago", "tomorrow at 9am") was based on the interpretation of the reference instant/timestamp using the system timezone rather than the assigned timezone (e.g., "April 5" in the system timezone may already "April 6" in the assigned timezone).
This changed some current relative date/time output. So, it is published in a minor version, instead of a patch.
v2.7.9Compare Source
e1acb29当日to本日8c415a8v2.7.8Compare Source
6d8d672257722fa857d3f80c126b6646c753a15d3dv2.7.7Compare Source
08e4dc431bcae3696d247d61f93323abddabe6e995v2.7.6Compare Source
3ae3144chrono.zhconfiguration from combinedzh.hansandzh.hantc5261b7v2.7.5Compare Source
d1a71c99aeb1c3fa472f23126f44v2.7.4Compare Source
c2011152cbe422fed9f9dv2.7.3Compare Source
4c4d6d15db3a1fv2.7.2Compare Source
cb0bdd4v2.7.1Compare Source
5db3a1fv2.7.0Compare Source
tags(Set<string>).v2.6.6Compare Source
ParsedComponentsagain (by @SferaDev) in https://github.com/wanasit/chrono/pull/520Full Changelog: wanasit/chrono@v2.6.5...v2.6.6
v2.6.5Compare Source
ReferenceWithTimezoneandParsingComponentsto public interface99b2e9f1b6994bv2.6.4Compare Source
v2.6.3Compare Source
timezonesoverride configuration665bda6)787c41b)v2.6.2Compare Source
b2b46379e992db(credit @JoakimNil)
v2.6.1Compare Source
8b64dcbv2.6.0Compare Source
v2.5.1Compare Source
6760ca0dc1b244v2.5.0Compare Source
Others:
v2.4.2Compare Source
v2.4.1Compare Source
Minor version v2.3 -> v2.4
Other:
a3c3bf8,a89da1d)v2.3.9Compare Source
chrono.ru) by @mikemikhaylov (#458)195976d0838c52v2.3.8Compare Source
f4964a6(by @PriyankaSand)668b5fe(by @georgd)v2.3.7Compare Source
0d1c9bdv2.3.6Compare Source
afbba58v2.3.5Compare Source
chrono.zh.hant) support from @DingWeizhe (MR #417)c4cd375v2.3.4Compare Source
543c3bc801ca4ev2.3.3Compare Source
d337a538efe94cv2.3.2Compare Source
699c871v2.3.1Compare Source
0cfef4ev2.3.0Compare Source
v2.2.7Compare Source
f03634577fbd83dde6103b9c02f5v2.2.6Compare Source
cdfb6bc053cc8f6a52cf3v2.2.5Compare Source
38cbefbfab8f51ac08a8clint-staged/lint-staged (lint-staged)
v15.5.2Compare Source
Patch Changes
5561321Thanks @YimingIsCOLD! - Correctly handle colon (:) characters in staged filenames.v15.5.1Compare Source
Patch Changes
#1533
5d53534Thanks @iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:v15.5.0Compare Source
Minor Changes
630af5fThanks @iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.Example with Prettier
By default Prettier prefers double quotes.
Previously
file.jswith only double quotes"changed to'git commit -am "I don't like double quotes"prettier --write file.js, converting all the'back to"'are stagedNow
file.jswith only double-quotes"changed to'git commit -am "I don't like double quotes"prettier --write file.js, converting all the'back to"v15.4.3Compare Source
Patch Changes
cbfed1dThanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.v15.4.2Compare Source
Patch Changes
8827ebfThanks @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.1Compare Source
Patch Changes
#1504
1c7a45eThanks @iiroj! - Default TypeScript config filenames match JS equivalents.#1504
9cc18c9Thanks @iiroj! - Add missing conditional exports syntax for TypeScript types.v15.4.0Compare Source
Minor Changes
#1500
a8ec1ddThanks @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
.tsfile extension for the configuration if your Node.js version supports it. The--experimental-strip-typesflag 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
9b79364Thanks @iiroj! - Handle possible failures when logging user shell for debug info.publint/publint (publint)
v0.3.12Compare Source
Patch Changes
#!(#183)v0.3.11Compare Source
Patch Changes
Update
EXPORTS_GLOB_NO_DEPRECATED_SUBPATH_MAPPINGmessage and severity to error (#179)Add a new warning when the
"exports"or"imports"field contain a fallback array as most tooling will only the pick the first value that can be parsed, and other tooling may work differently leading to inconsistent behaviors (#180)v0.3.10Compare Source
Patch Changes
Support custom conditions in
"exports"that points to raw TS or TSX files. This configuration is common in monorepo setups where packages refer to the raw files among themselves using a custom condition so custom aliasing isn't needed. (b34ea94)With this support, the
"types"condition is allowed to come after any exports of the raw TS or TSX files. File existence checks are also disabled for raw TS and TSX files reference as after publish these files may intentionally be not published.v0.3.9Compare Source
Patch Changes
Support the
formatMessageutility in the browser. It has a newcolor: 'html'option to highlight important parts with<strong>tags instead of ANSI colors. It also has a newreference: booleanoption so the messages are worded in reference of the message location. (e1cfef0)If
formatMessageis passed apackage.jsonobject with missing keys, the message part that references the value will now fallback to"undefined"instead of completely erroring out. (45962d1)v0.3.8Compare Source
Patch Changes
Support passing a tarball path to the publint CLI. This allows to easily lint any tarball files at hand. (#166)
The
publintAPI now returns apkgobject as a convenience to pass it toformatMessage(#166)Updated dependencies [
02d169b]:v0.3.7Compare Source
Patch Changes
The
"imports"field is now linted with the following rules: (#162)IMPORTS_KEY_INVALID: Ensure the imports key starts with a#IMPORTS_VALUE_INVALID: Ensure the imports value is a valid path that starts with a./IMPORTS_GLOB_NO_MATCHED_FILES: Ensure the imports glob matches at least one fileIMPORTS_DEFAULT_SHOULD_BE_LAST: Ensure the"default"condition is last in an entrypoint's objectIMPORTS_MODULE_SHOULD_BE_ESM: Ensure the"module"condition file is ESMIMPORTS_MODULE_SHOULD_PRECEDE_REQUIRE: Ensure the"module"condition precedes the"require"condition in an entrypoint's objectImprove SSH git URL detection when checking the
"repository"field. Values like"[email protected]:user/project.git"is now detected as a valid git URL, but will be suggested to use a full git URL instead, like"git+ssh://[email protected]/user/project.git"(28da844)Fix exports types message when the
"require"or"import"condition already exists but the dts file format is still invalid (a731ec3)v0.3.6Compare Source
Patch Changes
.jsor/index.js(04f289e)v0.3.5Compare Source
Patch Changes
Check the
"bin"field if the referenced file exists, has the correct JS format, and can be executed (#150)Deprecate the
depscommand. The command has been tricky to maintain and incomplete (e.g. doesn't lint recursively). A separate tool can be used to run publint on dependencies instead, e.g.npx renoma --filter-rules "publint". (#149)v0.3.4Compare Source
Patch Changes
When globbing
"exports"values that contains*, also respect"exports"keys that mark paths as null. For example: (b9605ae){ "exports": { "./*": "./dist/*", "./browser/*": null } }The glob in
"./*": "./dist/*"will no longer match and lint files in"./browser/*"as it's marked null (internal).Update logs when running the
publintCLI: (58d96a2)publintversion is now displayed.publint depscommand no longer logs passing dependencies. Only failing dependencies are logged.Examples:
$ npx publint deps $ Running publint v0.X.X for my-library deps... $ x my-dependency $ Errors: $ 1. ...Fix detecting shorthand repository URLs with the
.character (09d8cbb)Clarify message when
"types"is not the first condition in the"exports"field (5a6ba00)Correctly detect if a
"types"value in"exports"is used for dual publishing (3f3d8b2)v0.3.3Compare Source
Patch Changes
Rename
EXPORT_TYPES_INVALID_FORMATmessage toEXPORTS_TYPES_INVALID_FORMAT(#139)Allow versioned types conditions (e.g.
"types@>=5.2") in"exports"when checking for"types"condition ordering (#138)v0.3.2Compare Source
Patch Changes
(Potentially breaking) Disable running lifecycle scripts, such as
prepare,prepack, andpostpack, when running the pack command internally. This returns to the behavior in v0.2. (Note that this change does not apply to yarn as it does not support ignoring lifecycle scripts for local projects) (#128)This change is made as running lifecycle scripts was an unintentional behavior during the v0.3 breaking change, which could cause the linting process to take longer than expected, or even cause infinite loops if
publintis used in a lifecycle script.Update repository and bugs URLs to point to the new
publintorganization (1eda033)Updated dependencies [
1eda033,10e3891]:v0.3.1Compare Source
Patch Changes
#!(#183)v0.3.0Compare Source
Minor Changes
The
vfsoption is removed in favour of an extended support ofpack: { tarball: ArrayBuffer | ReadableStream }andpack: { files: PackFile[] }APIs. Now, it is even easier to usepublintin the browser or against a packed.tgzfile in Node.js. See the docs for more examples of how to use these new options. (#122)Bump node version support to >=18 (
cb2ed8b)publintnow runs your project's package manager'spackcommand to get the list of packed files for linting. The previousnpm-packlistdependency is now removed. (#120)A new
packoption is added to the node API to allow configuring this. It defaults to'auto'and will automatically detect your project's package manager usingpackage-manager-detector. See its JSDoc for more information of the option.This change is made as package managers have different behaviors for packing files, so running their
packcommand directly allows for more accurate linting. However, as a result of executing these commands in a child process, it may take 200-500ms longer to lint depending on the package manager used and the project size. The new handling also does not support yarn 1. See this comment for more information.If you use yarn 1, you should upgrade to the latest yarn version or a different package manager. Otherwise, no other changes are required for this new behavior.
Patch Changes
Initial setup to publish with Changesets (
24a62f5)When a dependency with the
file:orlink:protocol is specified in thepackage.json, it will now error to prevent accidentally publishing dependencies that will likely not work when installed by end-users (6e6ab33)Fix
EXPORT_TYPES_INVALID_FORMATlinting to detect.d.mtsand.d.ctsfiles (af5e88b)Updated dependencies [
d0b406b]:keithamus/sort-package-json (sort-package-json)
v2.15.1Compare Source
Bug Fixes
v2.15.0Compare Source
Features
stableVersion(#335) (e9ab5c6)v2.14.0Compare Source
Features
v2.13.0Compare Source
Features
Configuration
📅 Schedule: Branch creation - "after 10:00 before 19:00 every weekday except after 13:00 before 14:00" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.