Repository navigation
Prepare RC33 guided workflow integration candidate - #550
Merged
harrisonoconnorhover merged 3 commits intoOct 1, 2026
Merged
Conversation
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.
Prepare RC33 as a GitHub integration candidate so Druff and curated connectors can consume the merged graph preview, run explanation, and date-scoped repair behavior from one verified artifact. Public PyPI RC20 and the existing public-release promotion gate remain unchanged.
The curated catalog and Salesforce starter now pin Salesforce 0.3.2 and ServiceNow 0.2.3, preserving each package's actual minimum and accepting Dander below 0.10. Setup documentation explains upgrading a manifest and rebuilding the runtime. Both connector versions are now verified on PyPI: published requirements and downloaded wheel hashes match the tested builds. Their protected merges, exact-main checks, and trusted publishing workflows succeeded (Salesforce run 36864835715; ServiceNow run 36864843492).
The package version and lockfile advance together without dependency updates. Release metadata tests derive the prepared version; historical Redshift fixtures explicitly bind the RC32 launcher contract they exercise instead of silently following the current package version. Runtime benchmark rules and historical objective records remain unchanged. Notes identify the candidate's contract digest and remaining live/support limits.
Validation: 32 focused release/Redshift tests; Ruff lint/format; canonical strict typing (516 files); release metadata and contract drift checks; wheel/source build and distribution-content validation; git diff --check. The first full CI run exposed the five version-dependent fixture failures corrected here (2,510 other tests passed). Protected CI and exact-main CI are required before candidate publication.
The corrected version-only candidate passed all protected CI. Subsequent catalog/starter verification passed 42 focused tests plus all 10 catalog cases (including the retained 0.7 prerelease case), Ruff, strict typing and unchanged regenerated contracts. Final combined protected CI and exact-main CI remain required.