Repository navigation
Conversation
….6 asks for
`@antelopejs/dms-assistant` 0.2.6 (published 2026-11-15 10:00 UTC) supports
`@antelopejs/dms-frontend` >=0.11.6 <0.12.0. `antelope.config.ts` takes the
assistant from a range, so a build installs 0.2.6, while `pnpm-lock.yaml`
holds dms-frontend 0.11.4. `ajs-dms build` then stops:
✖ These frontend modules do not run on @antelopejs/dms-frontend 0.11.4
@antelopejs/dms-assistant-frontend-vue (./.antelope/cache/@antelopejs/dms-assistant@0.2.6/frontend-vue) supports >=0.11.6 <0.12.0
→ Install a @antelopejs/dms-frontend release in their ranges, or upgrade the modules
The floor in `package.json` moves to 0.11.6 and the lockfile to that release.
Same change as AntelopeJS/template-dms-demo#180.
Co-Authored-By: Claude <noreply@anthropic.com>
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.
What is broken
On main (
1a99dc3), the dashboard build stops:@antelopejs/dms-assistant0.2.6 was published on 2026-11-15 at 10:00 UTC and supports@antelopejs/dms-frontend>=0.11.6 <0.12.0(0.2.5 supported>=0.11.4).antelope.config.tstakes the assistant from a range, so a build installs 0.2.6.pnpm-lock.yamlholds dms-frontend 0.11.4. The backend builds.CI does not see it: it does not run
ajs-dms build.The change
package.json:@antelopejs/dms-frontend>=0.11.6 <0.12.0(was>=0.11.4 <0.12.0).pnpm-lock.yaml: dms-frontend 0.11.6.The same two lines as AntelopeJS/template-dms-demo#180, which was also checked by a deployment.
How it was checked
Locally only (Windows, Node 24, pnpm 10.33.0), on 2026-11-15 around 21:00 UTC, from an empty module cache:
pnpm install --frozen-lockfile,pnpm run build,ajs project build -e production(8 modules; from the ranges: api 1.7.5, auth-jwt 1.1.2, dms 0.20.7, dms-assistant 0.2.6, file-storage-local 0.2.1, mongodb 1.8.7, nodemailer 0.0.12), thenajs-dms build:Not started, not deployed.
What this does not fix
The next module release that raises the dms-frontend it supports does the same again: the modules move at each build,
pnpm-lock.yamldoes not (AntelopeJS/template-dms-demo#155).