Updating packages
@drawnagency packages follow a 0.1.x version range. Client sites use "^0.1.0" in package.json, which under semver 0.x rules means >=0.1.0 <0.2.0 — only patch releases are picked up automatically; a jump to 0.2.0 would require a manual update.
Automatic updates via Renovate
Section titled “Automatic updates via Renovate”Client sites ship with renovate.json pre-configured. Renovate opens a pull request when a new @drawnagency patch version is published. The configured behavior:
rangeStrategy: "bump"— Renovate bumps the version floor inpackage.json(e.g.^0.1.4→^0.1.5) rather than leaving a range that could be satisfied by a stale version.minimumReleaseAge: "3 days"— Renovate waits three days after a new version is published before opening the PR, providing a buffer to catch and retract a bad publish before it reaches client sites.automerge: true— Renovate merges the PR automatically once CI passes.
This means most updates reach the site within three days of publication without any manual action.
Forcing an immediate update
Section titled “Forcing an immediate update”To update @drawnagency packages right now, run from the client repo root:
pnpm update "@drawnagency/*"git add package.json pnpm-lock.yamlgit commit -m "chore: update @drawnagency packages"git pushNetlify picks up the push and deploys the updated site.
Always commit the lockfile
Section titled “Always commit the lockfile”Netlify installs with a frozen lockfile. The committed pnpm-lock.yaml is the exact set of packages that will be installed — if you update package.json without updating and committing pnpm-lock.yaml, the Netlify build will fail with a lockfile mismatch error.
Always commit package.json and pnpm-lock.yaml together.
Version range rules
Section titled “Version range rules”The ^0.1.0 range will not pick up a 0.2.0 or later release. If a future breaking change requires moving to 0.2.x, update the range in package.json manually:
{ "dependencies": { "@drawnagency/core": "^0.2.0", "@drawnagency/primitives": "^0.2.0" }}Then run pnpm install and commit both files. Check the release notes for migration steps before updating across a minor-version boundary.