| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Warning
Updates dependency resolution to force newer brace-expansion and js-yaml versions.
Changes:
| File | Description |
|---|---|
| package.json | Updates dependencies and overrides. |
| package-lock.json | Records the resolved dependency tree. |
| lib/entry-points.js | Generated bundle; excluded from review. |
Sorry, something went wrong.
| "@octokit/plugin-paginate-rest": { | ||
| "semver": ">=9.2.2" | ||
| }, | ||
| "brace-expansion": "^5.0.8", |
| "semver": ">=6.3.1" | ||
| }, | ||
| "glob": "^13.0.6", | ||
| "js-yaml": "^5.2.2", |
| Back | FazBrowse Home | New Git URL |
Adds overrides for brace-expansion and js-yaml to force newer versions.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
Products:
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist