chore(main): release engine-and-dependents libraries - #9780
Open
JSONbored wants to merge 3 commits into
Open
Conversation
Contributor
|
Important 🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ⏳ LoopOver is waiting…LoopOver has seen this pull request and is waiting on CI checks to finish before reviewing it. This comment will update once the review runs. 🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed · 🟨 Waiting |
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
JSONbored
force-pushed
the
release-please--branches--main--groups--engine-and-dependents
branch
from
July 29, 2026 09:02
9fb4376 to
054a865
Compare
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| 🔵 In progress View logs |
loopover-ui | 69c5823 | Jul 29 2026, 01:23 PM |
JSONbored
force-pushed
the
release-please--branches--main--groups--engine-and-dependents
branch
from
July 29, 2026 09:24
9edbfbf to
1017e59
Compare
JSONbored
force-pushed
the
release-please--branches--main--groups--engine-and-dependents
branch
from
July 29, 2026 09:45
7b84172 to
f6736c7
Compare
JSONbored
added a commit
that referenced
this pull request
Jul 29, 2026
…ished contract (#9797) apps/loopover-ui declared "@loopover/contract": "^0.1.0". While contract sat at 0.1.0 that matched the workspace copy and npm linked it. The moment release-please bumped contract into the engine-and-dependents group at 3.17.0, the range stopped matching -- and npm did NOT fail. It resolved the dependency from the REGISTRY, installing the published 0.1.0 tarball into apps/loopover-ui/node_modules while every other consumer used 3.17.0. The website would have built against a contract ~17 minor versions stale: same import specifiers, different schemas and types, no error anywhere. It surfaced only as an `npm ci` lockfile-sync failure on the release PR (#9780), which reads like a mechanical lockfile problem rather than the dependency bug it is. Pin the private apps to "*" -- the one range that means "the workspace copy" and cannot drift -- and add workspace-dep-ranges:check. The check requires "*" for PRIVATE packages rather than merely checking that a range is satisfied, because satisfaction alone cannot see the trap: `^0.1.0` against contract@0.1.0 is valid today and silently wrong the day contract is bumped. That rule caught a second latent instance, discovery-index pinning engine to ^3.4.0. Published packages keep real ranges (npm consumers need them) and are checked for satisfaction instead.
JSONbored
force-pushed
the
release-please--branches--main--groups--engine-and-dependents
branch
2 times, most recently
from
July 29, 2026 10:43
42959e5 to
79d8277
Compare
Bundle ReportBundle size has no change ✅ |
JSONbored
force-pushed
the
release-please--branches--main--groups--engine-and-dependents
branch
5 times, most recently
from
July 29, 2026 13:23
d30799e to
69c5823
Compare
JSONbored
force-pushed
the
release-please--branches--main--groups--engine-and-dependents
branch
2 times, most recently
from
July 29, 2026 14:46
dbb3c33 to
ac4ed90
Compare
JSONbored
force-pushed
the
release-please--branches--main--groups--engine-and-dependents
branch
from
July 29, 2026 15:32
46106d0 to
7479575
Compare
check-server-manifest requires server.json's version and packages[0].version to equal @loopover/mcp's, and release-please bumps the package without touching server.json -- so every release PR fails this check until the file is synced by hand. Automating that is #9874.
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
contract: 3.17.0
3.17.0 (2026-07-29)
Features
Fixes
engine: 3.17.0
3.17.0 (2026-07-29)
Features
Fixes
mcp: 3.17.0
3.17.0 (2026-07-29)
Features
Fixes
Dependencies
miner: 3.17.0
3.17.0 (2026-07-29)
Features
claim reclaimCLI to expire orphaned soft-claims (#9717) (edf0883), closes #9686Fixes
deny-hookssubcommand (#8933) (1eeaae1), closes #8851runwithloopin fleet-mode manifests (#9524) (6bb8588)Dependencies
This PR was generated with Release Please. See documentation.