Skip to content
This repository was archived by the owner on May 29, 2026. It is now read-only.

fix(deps): sync package-lock.json with preset 3.5.0 (unbreaks deploy)#56

Merged
rubenvdlinde merged 1 commit into
developmentfrom
chore/sync-lockfile-preset-3.4
May 18, 2026
Merged

fix(deps): sync package-lock.json with preset 3.5.0 (unbreaks deploy)#56
rubenvdlinde merged 1 commit into
developmentfrom
chore/sync-lockfile-preset-3.4

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Collaborator

Summary

PR #55 bumped `@conduction/docusaurus-preset` to `^3.4.0` in `package.json` without regenerating `package-lock.json`. CI uses `npm ci --legacy-peer-deps` which fails if the two are out of sync. Result: every Documentation workflow run on `development` since #55 merged has failed at `npm ci`, and the AI baseline (robots.txt, llms.txt, JSON-LD, OG card, sitemaps) never reached production on www.conduction.nl.

Fix

  • Bumped the package.json range from `^3.4.0` to `^3.5.0` to match the latest preset (also matches what the rest of the fleet was migrated to in chore(deps): preset lockfile 3.6.1 -> 3.6.2 (validator patch) #59-style PRs).
  • Regenerated `package-lock.json` against the new range using `npm install --package-lock-only --legacy-peer-deps --min-release-age=0` (the `min-release-age=0` override is documented in `.npmrc` as the way to pull fresh `@conduction/*` releases past the 24h cooldown).

Expected after merge

The next push to `development` will:

  1. `npm ci --legacy-peer-deps` succeeds (lock in sync)
  2. `docusaurus build` runs
  3. `postbuild` runs the AI-baseline validator (15 checks); should pass
  4. `upload-artifact` uploads `build/`
  5. `deploy` job downloads + pushes to `gh-pages`
  6. www.conduction.nl serves robots.txt, llms.txt, JSON-LD, og-conduction.png, both sitemaps

I'll verify the live state once the deploy completes.

Related

Test plan

PR #55 bumped @conduction/docusaurus-preset to ^3.4.0 in package.json
without regenerating package-lock.json. CI uses `npm ci --legacy-peer-deps`
which is strict about lockfile sync, so every Documentation workflow
run on development since #55 merged has failed at the install step.
The AI baseline never reached production.

This commit:
- Bumps the package.json range from ^3.4.0 to ^3.5.0 (the latest
  preset published — also matches what the rest of the fleet now uses).
- Regenerates package-lock.json against the new range.
- The cooldown rule in .npmrc (min-release-age=1) blocks fresh
  @conduction/* releases by default; this regen used
  --min-release-age=0 per the .npmrc comment.

After this lands, the documentation workflow should install cleanly,
the postbuild validate-ai-baseline check should pass, and the deploy
job should publish the AI baseline (robots.txt, llms.txt, JSON-LD,
og-conduction.png, sitemaps) to www.conduction.nl for the first time.
@rubenvdlinde rubenvdlinde merged commit 548cafb into development May 18, 2026
4 checks passed
@rubenvdlinde rubenvdlinde deleted the chore/sync-lockfile-preset-3.4 branch May 18, 2026 19:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant