Repository navigation
chore: release 0.3.1 - #31
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.
What this changes
Sets the package version to 0.3.1 and adds the 0.3.1 changelog entry for what merged since v0.3.0: automatic updates (PR #29) and the
Lantern-mac-arm64.ziprelease asset (PR #30). The owner tags v0.3.1 after the merge.Key files
package.json— version 0.3.0 to 0.3.1; the app manifest reads it from hereCHANGELOG.md— new[0.3.1] - 2026-11-10entry with Added and Changed, and the compare linksBefore / after
The app said 0.3.0; it says 0.3.1.
[Unreleased]compared v0.3.0...HEAD, now v0.3.1...HEAD, and[0.3.1]compares v0.3.0...v0.3.1.Verified with
pnpm run typecheck,pnpm run lintand the version-related tests, all green. Unreviewed fixes: none. Composed no primitives; wrote none. Lantern: 1 file re-mapped.Run cost