chore(release): cut engine v1.0.0 - #4686
Merged
JSONbored merged 3 commits intoJul 11, 2026
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | 2f86625 | Commit Preview URL Branch Preview URL |
Jul 11 2026, 06:30 AM |
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4686 +/- ##
=======================================
Coverage 94.27% 94.27%
=======================================
Files 451 451
Lines 38900 38900
Branches 14172 14172
=======================================
Hits 36674 36674
Misses 1574 1574
Partials 652 652
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
loopover-orb
Bot
added
gittensor:bug
JSONbored
force-pushed
the
release-please--branches--main--components--engine
branch
from
July 11, 2026 06:03
a4b8e83 to
7465930
Compare
7 tasks
…r the 1.0.0 cut npm ci failed on this branch with "Missing: @jsonbored/gittensory-engine@0.2.0 from lock file" -- gittensory-mcp and gittensory-miner both pinned ">=0.1.0 <1.0.0", which excludes this release's own 1.0.0 bump. Widens mcp to "^1.0.0" (release-please's node-workspace plugin, added on main, will keep this in sync automatically on every future bump) and miner to "*" (never published, no real external consumer). Also syncs packages/gittensory-miner/expected-engine.version to 1.0.0 (the engine-parity drift-check's pinned-version file) and de-hardcodes a test assertion in check-engine-parity-script.test.ts that pinned the live repo's exact engine version as a literal -- the same class of staleness this release just tripped, in a test this time.
JSONbored
approved these changes
Jul 11, 2026
github-project-automation
Bot
moved this to Todo
in Autonomous Miner System (Loopover AMS)
JSONbored
added this to the
Miner Wave 5 — AMS Hardening & Packaging (maintainer) milestone
github-project-automation
Bot
moved this from Todo
to Done
in Autonomous Miner System (Loopover AMS)
JSONbored
added a commit
that referenced
this pull request
Jul 11, 2026
gittensory-mcp and gittensory-miner both pinned "@jsonbored/gittensory-engine" to ">=0.1.0 <1.0.0" -- a range that excludes engine's own upcoming 1.0.0 release and breaks `npm ci` with a cryptic "Missing ... from lock file" error (PR #4686). This is a recurrence of the exact bug fixed by hand at the 0.1.0 -> 0.2.0 bump (#4179): any manually-chosen upper bound will eventually be exceeded by a future engine release. - gittensory-mcp: widen to "^0.2.0" (matches the current published engine version; release-please's node-workspace plugin now rewrites this automatically to track engine's version on every future bump, major or not, since it's a live externally-published package). - gittensory-miner: widen to "*" -- unlike gittensory-mcp, it has never been published (npm registry 404s on it today), so it has no real external consumer and no version-range supply-chain exposure; a same-monorepo workspace dependency is the idiomatic use for "*". Not onboarded into release-please management in this change since that's a separate release-process decision. - release-please-config.json: enable the node-workspace plugin (merge: false, matching the existing separate-pull-requests: true) so gittensory-mcp's dependency range is kept in sync automatically from here on, without ever needing a manual fix like this one again. Verified: npm ci resolves cleanly, full test suite passes, engine/mcp/ miner builds pass, mcp-pack/miner-pack smoke tests pass, all drift checks pass.
JSONbored
added a commit
that referenced
this pull request
Jul 11, 2026
…4974) gittensory-mcp and gittensory-miner both pinned "@jsonbored/gittensory-engine" to ">=0.1.0 <1.0.0" -- a range that excludes engine's own upcoming 1.0.0 release and breaks `npm ci` with a cryptic "Missing ... from lock file" error (PR #4686). This is a recurrence of the exact bug fixed by hand at the 0.1.0 -> 0.2.0 bump (#4179): any manually-chosen upper bound will eventually be exceeded by a future engine release. - gittensory-mcp: widen to "^0.2.0" (matches the current published engine version; release-please's node-workspace plugin now rewrites this automatically to track engine's version on every future bump, major or not, since it's a live externally-published package). - gittensory-miner: widen to "*" -- unlike gittensory-mcp, it has never been published (npm registry 404s on it today), so it has no real external consumer and no version-range supply-chain exposure; a same-monorepo workspace dependency is the idiomatic use for "*". Not onboarded into release-please management in this change since that's a separate release-process decision. - release-please-config.json: enable the node-workspace plugin (merge: false, matching the existing separate-pull-requests: true) so gittensory-mcp's dependency range is kept in sync automatically from here on, without ever needing a manual fix like this one again. Verified: npm ci resolves cleanly, full test suite passes, engine/mcp/ miner builds pass, mcp-pack/miner-pack smoke tests pass, all drift checks pass.
Merged
8 tasks
JSONbored
added a commit
that referenced
this pull request
Jul 12, 2026
…pat parsing (#5373) (#5463) Final stage of the gateCheckMode removal (stage 2.10/2.10): the RepositorySettings field itself was removed in #5459, but @jsonbored/gittensory-engine's own .gittensory.yml parser still recognized a bare settings.gateCheckMode key and derived reviewCheckMode from it for back-compat. Remove that derivation, the FocusManifestSettings type entry, and the deprecated field on manifest-deps-types.ts's RepositorySettings mirror. settings.gateCheckMode is now an unrecognized key: it parses into nothing and derives nothing. settings.reviewCheckMode remains the sole, unambiguous publish-authority key. Blast radius: parseFocusManifest/parseFocusManifestContent are the only public exports touched. @jsonbored/gittensory-mcp doesn't reference this code path at all; @jsonbored/gittensory-miner calls parseFocusManifestContent but never reads gateCheckMode/ reviewCheckMode from the result, and isn't itself published to npm. publish-engine.yml is workflow_dispatch-only, so merging this does not itself publish anything. The package.json version is already 1.0.0 (#4686, merged, not yet published -- npm still serves 0.2.0) -- bundling this breaking removal into that not-yet-shipped 1.0.0 is the right time to shed this back-compat parsing before the package commits to a stable surface, rather than requiring a separate future major bump for the same change. Also drops a now-dead SETTINGS_ALIAS_MANIFEST row in check-docs-drift.mjs left over from the RepositorySettings-level removal in #5459 (gateCheckMode is no longer iterated as a field to alias-check at all).
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
1 participant
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.0.0 (2026-07-10)
⚠ BREAKING CHANGES
Features
Fixes
This PR was generated with Release Please. See documentation.