Skip to content

chore: promote next to main#259

Merged
trek-e merged 30 commits into
mainfrom
next
May 25, 2026
Merged

chore: promote next to main#259
trek-e merged 30 commits into
mainfrom
next

Conversation

@trek-e

@trek-e trek-e commented May 25, 2026

Copy link
Copy Markdown
Collaborator

Administrative promotion of next into main via CLI as requested.

Solvely-Colin and others added 30 commits May 24, 2026 17:56
…gent-semver-comp

fix(10): consolidate semver comparison policy
…lint-misses-cros

fix(11): detect cross-name hand-sync pairs from allowlist
* fix(#17): enforce AskUserQuestion 4-option cap across workflows

* chore(changeset): add fixed entry for #17
* refactor(#179): migrate configuration module to sdk/src/config

* chore(#179): add changeset for config module path migration
* refactor(#180): migrate state document module to sdk/src/state

* test(#180): ratchet lint allowlists for state module relocation
…dule

refactor(#182): migrate project-root resolution module to sdk/src/runtime
…licy

refactor(#183): migrate runtime name policy module to sdk/src/runtime
refactor(#184): migrate init composer handlers to sdk/src/handlers/init
…fest

refactor(#185): migrate hub, errors, and manifest to canonical src seams
…lers

refactor(#186): split per-family handler maps into sdk/src/handlers
…ridge-crash

fix: avoid Windows current-timestamp crash by bypassing SDK bridge
…on (#242)

* docs(#15): propose convergence flag naming and doc-only test-gate exception

* docs(#15): define convergence config and allowed AI selection
@trek-e trek-e merged commit 2d32557 into main May 25, 2026
21 of 28 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Wrong target branch

This PR targets main but the source branch next is not a release, hotfix, critical-fix, or back-merge branch.

Most PRs should target next, not main. See docs/branching.md.

How to fix: click "Edit" next to the PR title above and change the base branch from main to next. No need to recreate the PR.

When IS it OK to target main?
  • release/X.Y.0 branches (cut by release.yml)
  • hotfix/X.Y.Z branches (cut by hotfix.yml)
  • fix/critical-* branches (production-down emergencies)
  • chore/backmerge-* branches (automated back-merge from this workflow)
  • revert/critical-* branches (emergency reverts of a bad merge on main)

@github-actions

Copy link
Copy Markdown
Contributor

Please use the PR template format

This PR is allowed to stay open because the author is a contributor or higher, but the body does not follow one of the required PR templates.

Please update the PR description to use the fix, enhancement, or feature template format from CONTRIBUTING.md so the automated documentation modules can do their job.

Detected problem: PR body does not match the fix, enhancement, or feature template.

@github-actions

Copy link
Copy Markdown
Contributor

Missing issue link — PR auto-closed

This PR does not reference an issue. All PRs must link to an open issue using a closing keyword in the PR body:

Closes #123

If no issue exists for this change, open one first, then update this PR body with the reference.

To resume work after fixing the body: edit the PR description to add a valid Closes #NNN, Fixes #NNN, or Resolves #NNN line, then click Reopen pull request. The workflow will re-evaluate on reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants