-
Notifications
You must be signed in to change notification settings - Fork 15
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
Update Non-critical tooling packages #714
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/non-critical-tooling-packages
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
This pull request is automatically being deployed by Amplify Hosting (learn more). |
renovate
bot
force-pushed
the
renovate/non-critical-tooling-packages
branch
2 times, most recently
from
February 7, 2024 07:01
f1b1b5c
to
cbd0746
Compare
renovate
bot
force-pushed
the
renovate/non-critical-tooling-packages
branch
from
February 14, 2024 12:51
cbd0746
to
c44d5c6
Compare
renovate
bot
changed the title
Replace Non-critical tooling packages
Update Non-critical tooling packages
Feb 14, 2024
renovate
bot
force-pushed
the
renovate/non-critical-tooling-packages
branch
from
February 14, 2024 16:35
c44d5c6
to
1ac8052
Compare
renovate
bot
force-pushed
the
renovate/non-critical-tooling-packages
branch
from
February 24, 2024 13:09
1ac8052
to
8e3d7bb
Compare
renovate
bot
force-pushed
the
renovate/non-critical-tooling-packages
branch
from
March 12, 2024 12:23
8e3d7bb
to
e036983
Compare
renovate
bot
force-pushed
the
renovate/non-critical-tooling-packages
branch
from
March 20, 2024 14:16
e036983
to
96d4a54
Compare
Quality Gate passedIssues Measures |
renovate
bot
force-pushed
the
renovate/non-critical-tooling-packages
branch
3 times, most recently
from
June 8, 2024 09:21
60e4b7a
to
da2cf7a
Compare
renovate
bot
force-pushed
the
renovate/non-critical-tooling-packages
branch
2 times, most recently
from
June 17, 2024 10:32
008f0f5
to
c9e2225
Compare
renovate
bot
force-pushed
the
renovate/non-critical-tooling-packages
branch
from
June 25, 2024 09:40
c9e2225
to
925d737
Compare
renovate
bot
force-pushed
the
renovate/non-critical-tooling-packages
branch
from
July 16, 2024 14:23
925d737
to
1c8760c
Compare
Quality Gate passedIssues Measures |
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:
^4.12.1
->^4.14.0
^4.1.5
->^5.0.0
^3.1.1
->^3.3.3
This is a special PR that replaces
npm-run-all
with the community suggested minimal stable replacement version.Release Notes
lirantal/lockfile-lint (lockfile-lint)
v4.14.0
Compare Source
Minor Changes
e0739b8829f158ba6f739759fcb41f03f3b60142
Thanks @lirantal! - fix: cosmiconfig dependency upgrade for better lockfile-lint config file supportv4.13.2
Compare Source
Patch Changes
889c016
Thanks @lirantal! - docs: update instructions for working with cosmiconfig filesv4.13.1
Compare Source
Patch Changes
2f7a477
Thanks @lirantal! - fix: support for validatio integrity exceptionUpdated dependencies [
2f7a477
]:v4.13.0
Compare Source
Minor Changes
ff74c61
Thanks @lirantal! - add --integrity-exclude CLI optionPatch Changes
ff74c61
]:prettier/prettier (prettier)
v3.3.3
Compare Source
diff
Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)
This change adds clarity to operator precedence.
Add parentheses for decorator expressions (#16458 by @y-schneider)
Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.
Support
@let
declaration syntax (#16474 by @sosukesuzuki)Adds support for Angular v18
@let
declaration syntax.Please see the following code example. The
@let
declaration allows you to define local variables within the template:For more details, please refer to the excellent blog post by the Angular Team: Introducing @let in Angular.
We also appreciate the Angular Team for kindly answering our questions to implement this feature.
v3.3.2
Compare Source
diff
Fix handlebars path expressions starts with
@
(#16358 by @Princeyadav05)v3.3.1
Compare Source
diff
Preserve empty lines in front matter (#16347 by @fisker)
Preserve explicit language in front matter (#16348 by @fisker)
Avoid line breaks in import attributes (#16349 by @fisker)
v3.3.0
Compare Source
diff
🔗 Release Notes
v3.2.5
Compare Source
diff
Support Angular inline styles as single template literal (#15968 by @sosukesuzuki)
Angular v17 supports single string inline styles.
Unexpected embedded formatting for Angular template (#15969 by @JounQin)
Computed template should not be considered as Angular component template
Use
"json"
parser fortsconfig.json
by default (#16012 by @sosukesuzuki)In v2.3.0, we introduced
"jsonc"
parser which adds trialing comma by default.When adding a new parser we also define how it will be used based on the
linguist-languages
data.tsconfig.json
is a special file used by TypeScript, it uses.json
file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing.json
file extension.We decide to treat it as a JSON file for now to avoid the extra configuration step.
To keep using the
"jsonc"
parser for yourtsconfig.json
files, add the following to your.pretterrc
filev3.2.4
Compare Source
diff
Fix incorrect parser inference (#15947 by @fisker)
Files like
.eslintrc.json
were incorrectly formatted as JSONC files.v3.2.3
Compare Source
diff
Throw errors for invalid code (#15881 by @fisker, @Josh-Cena, @auvred)
Fix parser inference (#15927 by @fisker)
v3.2.2
Compare Source
diff
Fix crash when parsing template literal CSS in a JSX style tag using a spread attribute (#15896 by @eelco)
For example this code would crash before:
Fix formatting error on optional call expression and member chain (#15920 by @sosukesuzuki)
v3.2.1
Compare Source
diff
Fix formatting error on member chain (#15915 by @sosukesuzuki)
v3.2.0
Compare Source
diff
🔗 Release Notes
Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.