Skip to content

Configure Renovate - #1

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure
Open

Configure Renovate#1
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Jul 7, 2026

Copy link
Copy Markdown

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


Detected Package Files

  • docker-compose.yml (docker-compose)
  • Dockerfile (dockerfile)
  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

Update dependency ws to v8.21.1
  • Schedule: ["at any time"]
  • Branch name: renovate/ws-8.x-lockfile
  • Merge into: main
  • Upgrade ws to 8.21.1

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR was generated by Mend Renovate. View the repository job log.

shoemoney pushed a commit that referenced this pull request Jul 8, 2026
Sub-project A of the hardening arc. Extract pure logic into src/lib.js
(vault, ipAllowed/ip2int, tokenMatches, safeStaticPath) so it can be
unit-tested in isolation; server.js keeps the http/db/ws wiring and now
guards listen()+poller behind an isMain check so tests can import it.

33 tests (node --test, no new deps): lib unit tests + black-box HTTP
tests on a throwaway DB. Each of the 4 bugs below has a regression test
that fails on the old logic and passes on the new:

  #1 static-file containment bypass — fp.startsWith(PUBLIC) with no path
     separator let a sibling dir (public-secret/) leak. Require boundary.
  #2 network gate spoofable — X-Forwarded-For was trusted from ANY client,
     so a direct caller could forge its source IP past AIGATE_ALLOW_CIDR.
     Now gated behind AIGATE_TRUST_PROXY=1 (secure by default).
  #3 auth compare could throw — string-length guard let timingSafeEqual
     throw on equal-strlen/diff-bytelen tokens → unhandledRejection/hang.
     tokenMatches guards on byte length and never throws.
  #4 ip2int accepted garbage — '999.1.1.1'/'abc' mapped to a number not
     null, weakening the CIDR gate. Now validates each octet 0..255.

BEHAVIOR CHANGE: #2 is secure-by-default. Set AIGATE_TRUST_PROXY=1 when
behind NPM so the gate/audit see the real client IP, not the proxy.
shoemoney added a commit that referenced this pull request Jul 18, 2026
- vaultOneKey helper (one home for the paste-mistake guards) now warns when a
  pasted key doesn't match the provider's catalog prefix — the catalog's 'prefix'
  data was previously unused; non-fatal, matches the existing warn philosophy. (F8)
- POST /api/keys/import: vault an array of {provider,key,label} in one call, one
  result row per key so a bad entry doesn't sink the batch (VISION pain #1). (F11)
- drop now-unused isKnownProvider import.
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.

0 participants