fix: harden link fixes and pre-release checks#97
Merged
Conversation
rogerdigital
marked this pull request as ready for review
July 24, 2026 07:34
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.
Summary
0.4.14and strengthen CI, package, coverage, and release-provenance checksWhy
Several pre-release paths could produce stale or overly broad fix actions, false scanner results, CLI/plugin behavior differences, or inconsistent release metadata. These changes keep automatic actions exact and make shipped artifacts verifiable.
Validation
npm run lintnpm run lint:obsidian-warningsnpm run buildnpm test— 23 files, 197 testsnpm run test:coverage— thresholds passednpm pack --dry-run— 8 expected files