Repository navigation
v0.7.0 - #31
Merged
Merged
v0.7.0#31
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.
v0.7.0
Replaces #30: that branch mixed breaking configuration changes into a patch release, so it ships here instead.
Breaking changes
--config <path>selects a trusted.ts/.mjs/.jsfile; an existing executable config now produces a migration error (exit 2) without running it.--no-configstill skips configuration and cannot be combined with--config.loadConfig(cwd)reads JSON instead of executing discovered code. UseloadConfig(cwd, { configPath: 'siro.config.mjs' }); the optional Node-version argument is nowoptions.nodeVersion.Migration: move data-only settings to
siro.config.json, or pass--config <path>for code you trust.Other changes
siro.config.jsonas data (built-in settings only), with precedence over a coexisting JS/TS config; invalid JSON fails without fallback.requireConfigKeypredicates as configuration errors (exit 2).Explicitly selected synchronous custom policies, decoded JSON schema 3, Node requirements and inspection scope remain unchanged. See the changelog.
pnpm verify(963 passed, 1 skipped) andpnpm test:packagepassed at391a418.Closes #21
Closes #22
Closes #23
Closes #24