Release the browser extension as 0.3.0 - #20
Merged
Merged
Conversation
The side panel inherits this release from @asksql/react: streamed output while a local model works, copy controls on prose and the result grid, cell tooltips, export feedback, and no red error while a schema answer is still being written. The extension's own sources are unchanged. package.json and manifest.json both carry the version. The release workflow checks the tag against package.json; the changelog guard reads the same file.
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.
Browser extension 0.3.0.
The extension has no source changes of its own. It bundles
@asksql/react, which landed in #19, sothis release carries those user-visible changes into the side panel:
for a minute with nothing moving.
turn failed for the whole second round trip, telling the reader to rephrase a question that was
being answered.
package.jsonandmanifest.jsonboth carry the version and are set to 0.3.0. The release workflowchecks the tag against
package.json, and the changelog guard reads the same file, so the two mustagree.