Skip to content

perf: dependency updates 20260616 - #33

Merged
weaponsforge merged 5 commits into
devfrom
perf/dependency-updates-20260616
Jun 16, 2026
Merged

perf: dependency updates 20260616#33
weaponsforge merged 5 commits into
devfrom
perf/dependency-updates-20260616

Conversation

@weaponsforge

@weaponsforge weaponsforge commented Jun 16, 2026

Copy link
Copy Markdown
Owner

Summary

  • Update dependencies to their latest versions

Library Updates

Library Old New
@redocly/cli 2.29.1 2.32.2
@types/node 25.6.0 25.9.3
eslint 10.2.1 10.5.0
express-rate-limit 8.3.2 8.5.2
globals 17.5.0 17.6.0
mongoose 9.5.0 9.7.0
tsc-alias 1.8.16 1.8.17
tsx 4.21.0 4.22.4
typescript-eslint 8.59.0 8.61.1
yaml 2.8.3 2.9.0
zod 4.3.6 4.4.3

Type of Change

  • Documentation
  • Other (please describe): maintenance - dependency updates

Checklist

Summary by CodeRabbit

  • Chores

    • Upgraded package version to 1.2.1
    • Updated core dependencies to latest versions including Mongoose, Zod, TypeScript tools, and ESLint
  • Documentation

    • Updated API reference viewer to the latest version
    • Improved formatting of API documentation specifications
    • Added guidance for updating and maintaining API documentation

- Updated @redocly/cli 2.29.1 -> 2.32.2
- Updated @types/node 25.6.0 -> 25.9.3
- Updated eslint 10.2.1 -> 10.5.0
- Updated express-rate-limit 8.3.2 -> 8.5.2
- Updated globals 17.5.0 -> 17.6.0
- Updated mongoose 9.5.0 -> 9.7.0
- Updated tsc-alias 1.8.16 -> 1.8.17
- Updated tsx 4.21.0 -> 4.22.4
- Updated typescript-eslint 8.59.0 -> 8.61.1
- Updated yaml 2.8.3 -> 2.9.0
- Updated zod 4.3.6 -> 4.4.3
- Run npm audit fix
  From 26 vulnerabilities (20 moderate, 6 high)
  To 13 moderate severity vulnerabilities
- Bump to version patch v1.2.1
@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@weaponsforge, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 47 minutes and 50 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c8c3b941-7b7c-484c-b149-ce7109b9a035

📥 Commits

Reviewing files that changed from the base of the PR and between be1ffae and 8a71b3d.

📒 Files selected for processing (2)
  • README.md
  • server/scripts/genSriHash.sh
📝 Walkthrough

Walkthrough

Adds a new Bash script (server/scripts/genSriHash.sh) to compute SHA-384 SRI hashes. Updates the Scalar API reference CDN embed to version 1.59.3 with a refreshed SRI hash. Reformats OpenAPI alternate-docs links from HTML lists to markdown/YAML lists. Bumps multiple server/package.json dependencies and updates the README with documentation steps and corrected paths.

Changes

API Documentation Maintenance and Dependency Updates

Layer / File(s) Summary
SRI hash script and Scalar CDN version bump
server/scripts/genSriHash.sh, server/public/index.html
Introduces genSriHash.sh which fetches a URL via curl, computes a sha384- digest with openssl, and prints the SRI value. Applies the output by bumping @scalar/api-reference from 1.52.5 to 1.59.3 and updating the integrity attribute in index.html.
OpenAPI alternate-docs link reformatting
server/public/openapi.json, server/public/openapi.yaml
Replaces the HTML <ul><li> block in the OpenAPI info.description with markdown-style formatting in the JSON file and a YAML list in the YAML file, covering Scalar, Swagger UI, and Redocly CLI links.
Package version and dependency bumps
server/package.json
Bumps package version to 1.2.1 and upgrades runtime deps (express-rate-limit, zod) and dev tooling (@redocly/cli, @types/node, tsc-alias, tsx, typescript-eslint, yaml, globals).
README documentation updates
README.md
Updates the Core Libraries/Frameworks table (removes Nodemon, bumps listed versions), adds an "Other Notes" section with Scalar update steps referencing genSriHash.sh, corrects docs:build output path to /server/public/redoc/index.html, and adds an SRI Hash Generator reference link.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

  • weaponsforge/ph-regions#31: Modifies the same Scalar CDN embed in server/public/index.html and the same OpenAPI alternate documentation description/link structure that this PR continues to update.

Poem

🐇 A hash is just a number, but trust must be earned,
I curl the script down, then let openssl churn,
sha384 encoded in base64 fine,
The integrity tag now matches each time.
New versions locked in, the YAML lists neat —
This bunny keeps docs tidy, from ears to feet! 🌿

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'perf: dependency updates 20260616' is overly vague and generic, using a broad term that doesn't clearly convey the specific nature of the changes beyond just mentioning 'dependency updates'. Consider a more descriptive title that highlights the main purpose, such as 'deps: update 11 dependencies to latest versions' or 'chore: bump dependencies and apply npm audit fixes' to provide better context.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch perf/dependency-updates-20260616

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 349-351: The documentation path mentioned in the `npm run
docs:build` section in README.md is incorrect. Update the documented output path
from `/server/public/redoc/index.html` to `public/docs/redoc/index.html` to
match the actual output location configured in server/package.json. This
correction ensures the documentation accurately reflects where the Redoc CLI
output is written.
- Around line 290-296: The SRI hash-generation command example in the README.md
documentation is incorrect. The bash script is actually named genSriHash.sh and
must be invoked with the ./ prefix, not as /server/scripts/genSriHash. Update
the code block example to show the correct command format:
./server/scripts/genSriHash.sh <full-script-url> so readers can properly
generate the SRI hash without encountering a missing-file error.

In `@server/scripts/genSriHash.sh`:
- Around line 13-14: The script currently uses curl with the -sL flags which
will silently hash HTTP error responses (like 404 pages), producing invalid SRI
hashes that break later. Add set -euo pipefail near the top of the script to
enable exit-on-error behavior, and replace the curl -sL flags in the hash
variable assignment with curl -fsSL, where the -f flag makes curl exit with an
error status on HTTP failures (4xx/5xx responses). This ensures the script fails
fast and prevents generating bogus SRI strings from error pages.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 73efc780-fc03-438b-b5ec-1d08b433aa6f

📥 Commits

Reviewing files that changed from the base of the PR and between 6237a7c and be1ffae.

⛔ Files ignored due to path filters (1)
  • server/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (6)
  • README.md
  • server/package.json
  • server/public/index.html
  • server/public/openapi.json
  • server/public/openapi.yaml
  • server/scripts/genSriHash.sh

Comment thread README.md
Comment thread README.md Outdated
Comment thread server/scripts/genSriHash.sh Outdated
@weaponsforge
weaponsforge merged commit e493631 into dev Jun 16, 2026
2 checks passed
@weaponsforge
weaponsforge deleted the perf/dependency-updates-20260616 branch June 16, 2026 01:44
@weaponsforge weaponsforge mentioned this pull request Jun 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant