You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,7 @@ syncpack fix -h
84
84
85
85
### [update](https://syncpack.dev/command/update)
86
86
87
-
Update packages to the latest versions from the npm registry, wherever they are in your monorepo.<br/>Semver range preferences are preserved when updating.
87
+
Update packages to the latest versions from the npm registry, wherever they are in your monorepo, including pnpm catalog entries in `pnpm-workspace.yaml`.<br/>Semver range preferences are preserved when updating.
Update dependencies in your monorepo to newer versions from the npm registry. Checks for available updates and modifies package.json files to use them. Unlike `fix` which synchronises versions across packages, `update` fetches the latest published versions. Use `--target` to control update strategy (latest, minor, patch).
24
+
Update dependencies in your monorepo to newer versions from the npm registry. Checks for available updates and modifies package.json files — and `pnpm-workspace.yaml` catalog entries when present — to use them. Unlike `fix` which synchronises versions across packages, `update` fetches the latest published versions. Use `--target` to control update strategy (latest, minor, patch). Versions newer than [minimumReleaseAge](CONFIG_MINIMUM_RELEASE_AGE) are excluded by default to reduce supply chain attack risk.
description: Skip updates to dependency versions published more recently than this threshold
4
+
sidebar:
5
+
badge: New
6
+
---
7
+
8
+
When using the [update](COMMAND_UPDATE) command, the minimum age (in minutes) a published version must reach before syncpack will consider it as an available update. Reduces supply chain attack risk by ignoring versions that have been on the registry for less time than the configured window — most malicious releases are detected and unpublished within an hour.
9
+
10
+
When this option is omitted from the [rcfile](TERM_RCFILE), syncpack reads `minimumReleaseAge` from the project's `pnpm-workspace.yaml` if present. When neither is set, it defaults to `1440` (one day). Setting `0` disables the filter.
11
+
12
+
## Default Value
13
+
14
+
```json title=".syncpackrc.json"
15
+
{
16
+
"minimumReleaseAge": 1440
17
+
}
18
+
```
19
+
20
+
## Examples
21
+
22
+
Wait one week before considering a published version:
23
+
24
+
```json title=".syncpackrc.json"
25
+
{
26
+
"minimumReleaseAge": 10080
27
+
}
28
+
```
29
+
30
+
Disable the filter and consider all published versions:
31
+
32
+
```json title=".syncpackrc.json"
33
+
{
34
+
"minimumReleaseAge": 0
35
+
}
36
+
```
37
+
38
+
Inherit the value already configured for [pnpm](HREF_PNPM_MINIMUM_RELEASE_AGE) by omitting it from the rcfile:
0 commit comments