chore(main): release dograh 1.45.0 - #609
Merged
Merged
Conversation
chewwbaka
force-pushed
the
release-please--branches--main--components--dograh
branch
4 times, most recently
from
August 3, 2026 07:33
d791ac5 to
de35608
Compare
| { | ||
| "name": "ui", | ||
| "version": "1.44.0", | ||
| "version": "1.45.0", |
There was a problem hiding this comment.
UI lockfile root metadata is stale for release 1.45.0
ui/package.json declares version 1.45.0, but ui/package-lock.json still declares 1.42.0 in both its top-level metadata and its root packages[""] entry. Update or regenerate the lockfile so its root package metadata matches the released UI package version.
Artifacts
Release metadata validation script
- The exact Python script parsed JSON and TOML, then compared the release manifest, API, UI, changelog, and UI lockfile metadata, the takeaway is that the check is reproducible.
Parent release metadata validation output
- The validator executed against the parent release and found its 1.42.0 UI lockfile root metadata stale relative to 1.44.0, the takeaway is that the mismatch predates this PR.
Release 1.45.0 metadata validation output
- The validator executed against the PR head and passed manifest/API/UI/changelog checks while failing both UI lockfile root-version checks, the takeaway is that the release metadata is not fully internally consistent.
UI lockfile installation output
- `npm ci --ignore-scripts` executed from `ui` and completed successfully with 1,166 packages installed, the takeaway is that the unchanged lockfile remains installable.
- `npm test` executed from `ui` and passed 13 test files with 58 tests, the takeaway is that the installed UI remains testable.
chewwbaka
force-pushed
the
release-please--branches--main--components--dograh
branch
21 times, most recently
from
August 10, 2026 13:37
14a7917 to
a594600
Compare
chewwbaka
force-pushed
the
release-please--branches--main--components--dograh
branch
2 times, most recently
from
August 11, 2026 12:51
d2397a3 to
c933d53
Compare
chewwbaka
force-pushed
the
release-please--branches--main--components--dograh
branch
2 times, most recently
from
August 11, 2026 15:05
ca025e8 to
37ba20a
Compare
chewwbaka
force-pushed
the
release-please--branches--main--components--dograh
branch
from
August 11, 2026 15:23
37ba20a to
be1713f
Compare
Contributor
Author
|
🤖 Created releases: 🌻 |
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.
🤖 I have created a release beep boop
1.45.0 (2026-08-11)
What's Changed
Features
Bug Fixes
base_urlfor theopenaiprovider → 401 with OpenAI-compatible endpoints (xAI/grok, local LLMs, proxies) #527) by @amaanJvd in fix(qa): forward configured base_url to QA analysis LLM (#527) #613Other Changes
New Contributors
Full Changelog: dograh-v1.44.0...dograh-v1.45.0
This PR was generated with Release Please. See documentation.
Greptile Summary
This release updates Dograh’s release manifest, API package version, UI package version, and generated 1.45.0 changelog. The potential stale UI lockfile-version concern was disproved:
npm cisucceeded andnpm pack --dry-runproducedui@1.45.0both before and after aligning the lockfile’s root version fields.Confidence Score: 5/5
The PR is safe to merge; no blocking failure remains.
The release metadata and changelog changes are consistent, and the exercised UI installation and packaging path reports version 1.45.0 despite the lockfile retaining older root metadata.
What T-Rex did
Reviews (29): Last reviewed commit: "chore(main): release dograh 1.45.0" | Re-trigger Greptile