AI-414: release v0.8.6-lsw.3 with the uppercase PR tag - #2
Merged
Merged
Conversation
Matches the PR-<n> convention the middleman already uses, so a test node overriding librechat.version reads the same on both.
… version npm ci validates the dependency tree, not the root version field, so syncing the lock bought nothing and guaranteed a conflict in a 1.6 MB generated file on every upstream tag merge.
beckerfelipee
changed the title
pipalols
approved these changes
Sep 1, 2026
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
2 participants
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.
Everything AI-414 still needs on the fork, in one release.
Uppercase pull request tag. A pull request build now publishes
PR-<n>instead ofpr-<n>, matching the convention the middleman already uses, so a node overridinglibrechat.versionreads the same on both. A Docker tag may contain uppercase; only the repository name may not. The workflow apull_requestevent runs comes from the pull request itself, so this build publishesPR-2and proves the change in one shot.package-lock.json goes back to the upstream blob.
npm civalidates the dependency tree, not the rootversionfield, so syncing the lock bought nothing and guaranteed a conflict in a 1.6 MB generated file on every upstream tag merge. Verified with a minimal repro:npm ciexits 0 with the root version out of sync.Version to
v0.8.6-lsw.3. Merging this publishes the image and creates the git tag.The old lowercase
pr-1stays in GHCR pointing at its last build and is never updated again. A node overridinglibrechat.versionhas to move to the uppercase tag.Supersedes #1.
AI-414