Prepare octagonal-wheels 0.1.53 - #48
Merged
Merged
Conversation
vrtmrz
marked this pull request as ready for review
August 13, 2026 09:05
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.
Prepare the compatible octagonal-wheels 0.1.53 patch release with generated declaration mappings for legacy TypeScript resolution.
Summary
libVersion(); andupdates.md.Version choice
This is a compatible patch release. It adds generated declaration metadata for existing public subpaths without changing runtime exports or the supported import surface.
Verification
npm run verify:workspacegate;typesVersionsmappings match the 233 existing public subpaths.The octagonal-wheels tarball contained the expected licence, README, compiled JavaScript, declarations, source maps, guide, and package metadata. It did not include workspace applications or test sources.
Validation boundary
This release changes package declaration metadata only. It does not change runtime or visible Obsidian behaviour, so no additional device validation is required before merging. The exact registry artefact must still be installed and checked in Self-hosted LiveSync before promotion from
nexttolatest.