chore: align with Raintree standard#25
Draft
admin-raintree wants to merge 6 commits into
Draft
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Classification
raintree-technology/agent-startercreate-agent-starter) using npm +package-lock.jsonbun.lockChanges
site/Bun checks ata99e879574108241a5fc7e96479512b135248d2a, passing the same SHA asstandard-ref.standard-ref.renovate.jsonextending the org base config..npmrc..nvmrcwith Node 22 while preserving the root package's existing>=18.0.0published runtime contract.site/bun.lock.@biomejs/biome@2.4.16, Biome configs,checkscripts, and formatted the configured JS/TS surface.claude-starterrepo toagent-starter.Commands And Results
Baseline, before changes:
npm ci- pass, 0 vulnerabilitiesbun install --frozen-lockfileinsite/- passnpm run lint- passnpm test- pass, 50 testsnpm audit --audit-level=moderate- pass, 0 vulnerabilitiesnpm pack --dry-run- pass, 223 package filesbun auditinsite/- pass, no vulnerabilitiesbun run lintinsite/- passbun run typecheckinsite/- passbun run buildinsite/- pass, Next generated 10 routesPost-change:
npm ci- pass, 0 vulnerabilitiesbun install --frozen-lockfileinsite/- pass, no lockfile changesnpm run check- pass, Biome checked 45 filesnpm run lint- passnpm test- pass, 50 testsnpm audit --audit-level=moderate- pass, 0 vulnerabilitiesnpm pack --dry-run- pass, 223 package filesbun run checkinsite/- pass, Biome checked 21 filesbun run lintinsite/- passbun run typecheckinsite/- passbun run buildinsite/- pass, Next generated 10 routesbun auditinsite/- pass, no vulnerabilitiesnode /tmp/raintree-standardization/.github/scripts/check-pinned-deps.mjsat repo root - passnode /tmp/raintree-standardization/.github/scripts/check-pinned-deps.mjsinsite/- passSTANDARD_DIR=/tmp/raintree-standardization/.github bash /tmp/raintree-standardization/.github/scripts/drift-check.sh- pass, no drift detectednode bin/cli.js init /tmp/raintree-standardization/agent-starter-cli-verify/codex --yes --agent codex --profile minimal- pass, wroteAGENTS.mdand.codex/skills/toon-formatter/SKILL.mdnode bin/cli.js init /tmp/raintree-standardization/agent-starter-cli-verify/cursor --yes --agent cursor --profile minimal- pass, wrote.cursor/rules/agent-starter.mdcand.cursor/rules/toon-formatter.mdcCompliance Matrix
/tmp/raintree-standardization/agent-starter.chore/raintree-standardfromorigin/main; no existing remote branch was overwritten.npm ciandbun install --frozen-lockfilepass..nvmrc/CI use Node 22; root package engine remains>=18.0.0to avoid changing its published runtime contract.../tsconfig.base.json.renovate.json.site/.env.exampleretained; no secrets added.NEEDS-HUMAN
None.
REVIEW-CLOSELY
site/biome.jsonchas a targeted override for JSON-LDdangerouslySetInnerHTMLinsite/app/page.tsx; the payload is local metadata serialized with<escaping.engines.noderemains>=18.0.0; raising it would be a package compatibility decision.