chore(release): version packages#28
Open
github-actions[bot] wants to merge 1 commit into
Open
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
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.
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
@sentiness/check-sdk@0.4.0
Minor Changes
CheckContext.repoRootso checks can reach the repository root independentlyof
cwd. In a polyglot monorepocwdis the zone root (e.g.crates/engine)while
repoRootis the repository root, for the rare check that needs repo-levelcontext. Additive and backward-compatible for the documented consumer pattern
(checks read the context); single-zone runs set
repoRoot === cwd.@sentiness/adapters@0.1.4
Patch Changes
@sentiness/check-biome@0.1.3
Patch Changes
@sentiness/check-coverage@0.1.3
Patch Changes
@sentiness/check-dependency-cruiser@0.1.3
Patch Changes
@sentiness/check-deps-diff@0.1.3
Patch Changes
@sentiness/check-eslint@0.1.3
Patch Changes
@sentiness/check-jscpd@0.1.3
Patch Changes
@sentiness/check-knip@0.2.2
Patch Changes
@sentiness/check-lockfile-lint@0.1.3
Patch Changes
@sentiness/check-osv-scanner@0.1.3
Patch Changes
@sentiness/check-playwright@0.1.3
Patch Changes
@sentiness/check-semgrep@0.1.3
Patch Changes
@sentiness/check-stryker@0.1.3
Patch Changes
@sentiness/cli@0.2.1
Patch Changes
@sentiness/core@1.0.1
Patch Changes
resolveZoneszone resolver (packages/core/src/zones), thefoundation for Phase V2 per-zone execution. It maps a v2 config's
zonesintorooted, option-merged placements (
absRoot = join(repoRoot, path); catalogoptions deep-merged with per-zone overrides). No public API change — the module is
internal to
coreand not re-exported fromindex.ts.@sentiness/_test-utils@0.1.3
Patch Changes