feat(migrations): add 0.7→1.0 migration recipe#315
Open
vkgeorgia wants to merge 1 commit into
Open
Conversation
Provides the MAJOR-release migration recipe for adopters upgrading from methodology 0.7 to 1.0. Covers all breaking changes whose deprecation windows close at the 1.0 cut: - Transform A: ACTIVITY → ACTION rename (element TYPE, IDs, file names, root array key, activity_type field, action-card files) - Transform B: INFORMATION_ENTITY → BUSINESS_OBJECT rename (IDs, file names, information_entities field) - Transform C: report_type now required on compliance-impact views (codemod detects missing field; adopter adds it manually) - Transform D: deprecated abbreviated prefix IDs become hard errors (ACT-, CHG-, FAC-, FACTOR- grace period, SCEN-, SCN-) Deliverables: README.md (manual steps), codemod.mjs (idempotent automated transforms A/B/D + C detection), validate.mjs (post-migration check; exits 0 on clean repo), and fixtures/before + after. Also extends scripts/check-notations.mjs allowlist for the new recipe files that intentionally carry non-current version pins. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Valerii Korobeinikov <vkgeorgia@icloud.com>
3 tasks
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.
Summary
migrations/0.7-to-1.0/— the MAJOR-release migration recipe covering all breaking changes whose deprecation windows close at the 1.0 cutREADME.md— manual migration guide (four transforms, step-by-step)codemod.mjs— idempotent automated script for Transforms A/B/D; detects Transform C missesvalidate.mjs— post-migration check; exits 0 on a clean repofixtures/before+fixtures/after— minimal adopter-repo snapshots demonstrating each transformscripts/check-notations.mjs— allowlist extended for the new recipe files (which intentionally carry non-current version pins)Breaking changes covered:
activity_typefield, action-card files)information_entities:key)report_typerequired on*.compliance-impact.transitrix.yaml(detected; manual fix)ACT-,CHG-,FAC-,FACTOR-(grace period closes),SCEN-,SCN-Test plan
node migrations/0.7-to-1.0/codemod.mjs fixtures/before --dry-runcorrectly identifies 2 files to change and 1 compliance-impact missnode migrations/0.7-to-1.0/validate.mjs fixtures/beforeexits 1 with 6 violationsnode migrations/0.7-to-1.0/validate.mjs fixtures/afterexits 0 (clean)node scripts/check-notations.mjspasses clean🤖 Generated with Claude Code