Version Packages - #90
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
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 master, this PR will be updated.
Releases
@noormdev/cli@1.4.0
Minor Changes
685b125: Show download progress while the TUI installs an update
The updater has always emitted byte counts every 512KB, and the CLI has always
rendered them, but the TUI's update screen ignored them: a ~70MB binary
download sat behind a bare spinner for its whole duration, indistinguishable
from a hang. The installing state now shows received and total megabytes, a
percent, and a progress bar, falling back to megabytes alone when the server
sends no
Content-Length. A stalled attempt that resumes says so, and keepsthe progress it had, because the retry resumes from the bytes already on disk.
@noormdev/sdk@1.4.0
@noormdev/example-llm-memory-db-mssql@0.0.7
Patch Changes
@noormdev/example-llm-memory-db-pg@0.0.7
Patch Changes
@noormdev/example-todo-db@0.0.7
Patch Changes