chore: version packages#42
Merged
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@effect-migrate/cli@0.4.0
Minor Changes
#41
f22c2ddThanks @aridyckovsky! - Add normalized schema for 40-70% audit.json size reduction and move business logic to coreBreaking Changes:
byFile/byRulewith deduplicatedrules[],files[],results[]arraysgroupsfield for O(1) lookupinfocounter to FindingsSummary (previously counted as warnings)@effect-migrate/cli/loaders/config- use@effect-migrate/coreexports instead@effect-migrate/cli/loaders/presets- usePresetLoaderservice insteadNew @effect-migrate/core exports:
Config utilities:
mergeConfig(defaults, userConfig)- Merge preset defaults with user configdeepMerge(target, source)- Deep merge plain objects (arrays replaced, not concatenated)isPlainObject(value)- Type guard for plain objectsPreset loading:
PresetLoader- Context.Tag for preset loading servicePresetLoaderService- Service interfacePresetLoaderNpmLive- Default Layer for npm-based preset resolutionPresetLoadError- Tagged error for preset loading failuresPreset- Preset type (rules + optional defaults)LoadPresetsResult- Result of loading multiple presetsRule construction:
rulesFromConfig(config)- Build rules from config (pattern + boundary)Schema enhancements:
presets?: string[]field for preset namesNormalizer utilities:
normalizeResults(results, config, threads?)- Convert to normalized schemaexpandResult(normalized)- Convert back to flat formatderiveResultKey(result)- Generate stable content-based key@effect-migrate/cli changes:
New workspace-aware preset resolution:
PresetLoaderWorkspaceLive- Layer that tries workspace path first, falls back to npmpathToFileURL()Refactored loaders:
loadRulesAndConfig()now orchestrates core services instead of implementing logicEffect.catchTag("PresetLoadError")for precise error handlingBuild improvements:
test/directories)Migration guide:
If you were importing from CLI loaders:
Test coverage:
Patch Changes
#41
cbd8eb9Thanks @aridyckovsky! - Update all READMEs to reflect current architecture and published usageDocumentation improvements:
Key updates:
Resolves chore: consolidate and update README to reflect actual usage #24
Updated dependencies [
f22c2dd,cbd8eb9]:@effect-migrate/core@0.4.0
Minor Changes
#41
f22c2ddThanks @aridyckovsky! - Add normalized schema for 40-70% audit.json size reduction and move business logic to coreBreaking Changes:
byFile/byRulewith deduplicatedrules[],files[],results[]arraysgroupsfield for O(1) lookupinfocounter to FindingsSummary (previously counted as warnings)@effect-migrate/cli/loaders/config- use@effect-migrate/coreexports instead@effect-migrate/cli/loaders/presets- usePresetLoaderservice insteadNew @effect-migrate/core exports:
Config utilities:
mergeConfig(defaults, userConfig)- Merge preset defaults with user configdeepMerge(target, source)- Deep merge plain objects (arrays replaced, not concatenated)isPlainObject(value)- Type guard for plain objectsPreset loading:
PresetLoader- Context.Tag for preset loading servicePresetLoaderService- Service interfacePresetLoaderNpmLive- Default Layer for npm-based preset resolutionPresetLoadError- Tagged error for preset loading failuresPreset- Preset type (rules + optional defaults)LoadPresetsResult- Result of loading multiple presetsRule construction:
rulesFromConfig(config)- Build rules from config (pattern + boundary)Schema enhancements:
presets?: string[]field for preset namesNormalizer utilities:
normalizeResults(results, config, threads?)- Convert to normalized schemaexpandResult(normalized)- Convert back to flat formatderiveResultKey(result)- Generate stable content-based key@effect-migrate/cli changes:
New workspace-aware preset resolution:
PresetLoaderWorkspaceLive- Layer that tries workspace path first, falls back to npmpathToFileURL()Refactored loaders:
loadRulesAndConfig()now orchestrates core services instead of implementing logicEffect.catchTag("PresetLoadError")for precise error handlingBuild improvements:
test/directories)Migration guide:
If you were importing from CLI loaders:
Test coverage:
Patch Changes
#41
cbd8eb9Thanks @aridyckovsky! - Update all READMEs to reflect current architecture and published usageDocumentation improvements:
Key updates:
Resolves chore: consolidate and update README to reflect actual usage #24
@effect-migrate/preset-basic@0.3.1
Patch Changes
f22c2dd,cbd8eb9]: