chore(release): weekly cadence bump — 2026-07-19#1959
Merged
Conversation
… 0.7.3, enterprise 0.3.3
E2E Test ResultsE2E Test Results - July 19, 2026Summary
Test Results
Generated by skillsmith E2E test suite |
…-release SMI-5057's M-5 test asserted cli's @smith-horn/enterprise peerDependency stays '*' after a core-only bump, on the premise that enterprise isn't in PACKAGE_SPECS. SMI-5120 added it there, and the test's own writeFileSync mock passes through to the real fs.writeFileSync while readFileSync is never mocked at all -- so the test reads/writes the actual checked-out packages/cli/package.json, not a fixture. Last week's release-cadence branch happened not to touch enterprise's version, so cli's real on-disk peer dep was still '*' when the test ran and the hardcoded assertion held by coincidence. This week's --all=patch bumped enterprise too (0.3.2 -> 0.3.3), so the real file already contains '^0.3.3' by the time the test reads it, and the hardcoded '*' literal no longer matches. The already-committed release bump itself is correct -- enterprise's peerDependenciesMeta already marks it optional, so this can't break public installs. Capture the pre-call value and assert against that instead of a literal, so the test verifies the actual behavioral contract (unchanged by a call that doesn't bump this key) regardless of what state the real file is in. Also corrects a stale doc-comment on updateWorkspaceDependencies that still claimed enterprise is absent from PACKAGE_SPECS. Verified: full root vitest suite (866 files / 14387 tests, all green), typecheck, lint -- all clean in this worktree's own container. Refs SMI-5057, SMI-5120 Co-Authored-By: claude-flow <ruv@ruv.net> Co-Authored-By: Claude <noreply@anthropic.com>
Auto-closed by release-cadence PR staleness watcher (SMI-4779)This PR is stale: 32h old, 10 commits behind main. Auto-closing rather than auto-rebasing because lockfile/changelog/version conflicts during rebase create silent broken PRs. RecoveryTo re-cut a fresh release PR from current main: See docs/internal/runbooks/release-cadence-stale-pr.md for the full operator runbook. Workflow run: https://github.com/smith-horn/skillsmith/actions/runs/29749112044 |
E2E Test ResultsE2E Test Results - July 20, 2026Summary
Test Results
Generated by skillsmith E2E test suite |
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.
Automated weekly release cadence PR opened by
release-cadence.yml(SMI-4191).What this PR does
Runs
scripts/prepare-release.ts --all=patchto bump all packages by one patch version and drain per-package CHANGELOG[Unreleased]sections into the new versions.What to check before merging
prepare-release.tswith the right flags locally, and open a manual PR.After merging
Trigger publish:
gh workflow run publish.yml -f dry_run=false. Thecreate-gh-releasejob will create matching GitHub Releases automatically.Parent: SMI-4144. See ADR-114.