@sentry/junior-maintenance 0.222.0 → 0.223.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -32,7 +32,11 @@ Verify the target exists for every inventoried package before mutating files:
|
|
|
32
32
|
pnpm view <package>@<target> version
|
|
33
33
|
```
|
|
34
34
|
|
|
35
|
-
|
|
35
|
+
Allow for npm security scanning and propagation delays after publication:
|
|
36
|
+
|
|
37
|
+
- If a version or tarball is missing, retry affected packages after 30, 60, and 120 seconds. Keep the same target; do not retry auth failures as publication delays.
|
|
38
|
+
- Confirm missing versions with cache-busted npm metadata and the direct version endpoint. Continue only when every package's exact target version and tarball are available.
|
|
39
|
+
- If still unavailable, leave app files unchanged and do not open an update PR. Report "not yet available on npm" with the target, affected packages, and checks. Missing packages alone do not prove a failed publish or a scanning delay; do not republish or cut another release.
|
|
36
40
|
|
|
37
41
|
### 3. Build release context
|
|
38
42
|
|
|
@@ -133,7 +137,7 @@ When asked to keep an app current whenever Junior publishes a release, resolve `
|
|
|
133
137
|
|
|
134
138
|
## Stop conditions
|
|
135
139
|
|
|
136
|
-
- Any Junior package lacks the target version
|
|
140
|
+
- Any Junior package still lacks the target version or tarball after the bounded availability checks in step 2.
|
|
137
141
|
- Any npm version in `(old_version, target_version]` lacks a matching GitHub release.
|
|
138
142
|
- `pnpm install --frozen-lockfile` fails after repair.
|
|
139
143
|
- Checks fail for non-pre-existing, non-environment reasons and no safe config fix is available from step 7.
|